Vulnerability in btrfs: Verify the Transaction ID of Dirty Extent Buffer

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001586: btrfs: verify the tranisd of the to-be-written dirty extent buffer. Affects Kernel versions < 17a2437d44f4bfa1f199343075e6458303a2dceb. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The btrfs package is a file system for Linux that provides advanced features such as snapshots, pooling, and checksums. It is designed to be efficient and scalable, making it suitable for both personal and enterprise use. However, a vulnerability has been discovered in btrfs that could potentially lead to security issues.

Vulnerability Detail

The vulnerability in btrfs involves the verification of the transaction ID (tranisd) of a dirty extent buffer before it is written. If this verification is not performed correctly, it could allow an attacker to manipulate the buffer and potentially execute arbitrary code or cause a denial of service. The impact and attack plausibility of this vulnerability have not been proven, but it is important to address it to ensure the security of systems using btrfs.

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

There is no specific workaround mentioned for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in btrfs related to the verification of the transaction ID of dirty extent buffers can potentially lead to security issues. It is crucial to update the Linux Kernel to version v5.16.19 or later to mitigate the risk associated with this vulnerability. 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 provides advanced features such as snapshots, pooling, and checksums. It is designed to be efficient and scalable.

The impact of this vulnerability is not proven, but it could potentially allow an attacker to manipulate a dirty extent buffer and execute arbitrary code or cause a denial of service.

To fix this vulnerability, update the Linux Kernel to version v5.16.19 or later, which includes the necessary fix for the verification of the transaction ID.

There is no specific workaround mentioned for this vulnerability. It is recommended to update the Linux Kernel to apply the fix.

You can find more information about this vulnerability in the Open Source Vulnerability database entry GSD-2022-1001586.

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