Use After Free Vulnerability in dm btree remove

Kernel Updated 02 Oct 2025

Summary

27/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002651: dm btree remove: fix use after free in rebalance_children(). Affects Kernel versions < 293f957be5e39720778fb1851ced7f5fba6d51c3. 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 dm btree remove vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. The dm btree remove function is part of the device-mapper subsystem, which allows for the creation of virtual block devices. This vulnerability specifically impacts the rebalance_children() function within dm btree remove.

Vulnerability Detail

The use after free vulnerability in rebalance_children() within dm btree remove can be exploited by an attacker to execute arbitrary code or cause a denial of service. This vulnerability occurs when the function attempts to rebalance the child nodes of a B-tree data structure, but fails to properly handle a use after free condition. By manipulating the B-tree structure in a specific way, an attacker can trigger the use after free, leading to memory corruption and potentially allowing them to gain control over the system.

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

If updating the Kernel is not immediately feasible, a possible workaround is to disable the use of the dm btree remove function or the device-mapper subsystem altogether. However, this may impact the functionality of certain applications or system components that rely on these features. It is strongly recommended to prioritize updating the Kernel to the patched version as soon as possible.

Conclusion

The use after free vulnerability in dm btree remove within the Kernel package can have severe consequences, including arbitrary code execution and denial of service. It is crucial to update the Kernel to the patched version as soon as possible to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use after free vulnerability in dm btree remove can allow an attacker to execute arbitrary code or cause a denial of service. This can potentially lead to a complete compromise of the affected system.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there are no known public exploits for this vulnerability. However, it is important to apply the patch as soon as possible to prevent any potential exploitation.

This vulnerability requires local access to the system in order to exploit it. However, if an attacker gains local access, they can potentially exploit this vulnerability to gain control over the system.

The primary mitigation for this vulnerability is to update the Linux Kernel to the patched version. Additionally, disabling the dm btree remove function or the device-mapper subsystem can serve as a temporary workaround, although it is recommended to prioritize the Kernel update.

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