Vulnerability in btrfs: fixup error handling in fixup_inode_link_counts

Kernel Updated 02 Oct 2025

Summary

25/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000782: btrfs: fixup error handling in fixup_inode_link_counts. Affects Kernel versions < 48568f3944ee7357e8fed394804745bd981e978a. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The btrfs package is a file system for Linux that provides advanced features such as snapshots, pooling, and checksums. It is widely used in various Linux distributions. The fixup_inode_link_counts function in btrfs is responsible for correcting the link counts of inodes. However, a vulnerability has been discovered in this function that could lead to potential security issues.

Vulnerability Detail

The vulnerability in btrfs's fixup_inode_link_counts function arises from a lack of proper error handling. When encountering certain errors during the fixup process, the function fails to handle them correctly, potentially leaving the file system in an inconsistent state. An attacker could exploit this vulnerability to cause data corruption or even execute arbitrary code with elevated privileges. The vulnerability was introduced in an unknown version and has been fixed in Linux Kernel version v5.10.43 by commit 48568f3944ee7357e8fed394804745bd981e978a.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, users can avoid the vulnerability by disabling the use of the btrfs file system until an updated kernel version is available. This can be achieved by switching to an alternative file system or using an older kernel version that is not affected by the vulnerability.

Conclusion

In conclusion, the btrfs package in Linux Kernel is vulnerable to a security issue in the fixup_inode_link_counts function. This vulnerability can be mitigated by updating the kernel to version v5.10.43 or later. Alternatively, users can disable the use of the btrfs file system until an updated kernel version is available. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

Btrfs is a file system for Linux that offers advanced features like snapshots, pooling, and checksums.

The fixup_inode_link_counts function in btrfs is responsible for correcting the link counts of inodes.

This vulnerability could lead to data corruption or arbitrary code execution with elevated privileges.

To fix this vulnerability, update the Linux Kernel to version v5.10.43 or later.

Yes, users can avoid the vulnerability by disabling the use of the btrfs file system.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback