Vulnerability in btrfs Direct IO Write Path in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000990: btrfs: release correct delalloc amount in direct IO write path. Affects Kernel versions >= f0bfa76a11e93d0fe2c896fcb566568c5e8b5d3f, < a04d37ddfe4be431b9e52e8504490376ab0a39a4. 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 compression. It is widely used in various Linux distributions. The direct IO write path is responsible for handling direct input/output operations, bypassing the page cache. This vulnerability affects the btrfs package in the Linux Kernel.

Vulnerability Detail

The vulnerability in the btrfs direct IO write path results in an incorrect release of delalloc (delayed allocation) amount. Delalloc is a mechanism used by file systems to allocate disk space on-demand when a file is written. Due to the incorrect release of delalloc, it may lead to resource leaks and potential denial-of-service attacks. The vulnerability was introduced in version v5.17 of the Linux Kernel and is fixed in version v5.17.4.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.4 or later. This can be done by downloading the latest stable version of the Linux Kernel from the official repository and following the installation instructions provided. After updating the Kernel, the vulnerability should be resolved.

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.

Conclusion

The vulnerability in the btrfs direct IO write path can be fixed by updating the Linux Kernel to version v5.17.4 or later. 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 compression.

The direct IO write path is responsible for handling direct input/output operations, bypassing the page cache.

Delalloc is a mechanism used by file systems to allocate disk space on-demand when a file is written.

The incorrect release of delalloc amount may lead to resource leaks and potential denial-of-service attacks.

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

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.4 or later. This can be done by downloading the latest stable version of the Linux Kernel from the official repository and following the installation instructions provided. After updating the Kernel, the vulnerability should be resolved.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.