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-1002699: dm btree remove: fix use after free in rebalance_children(). Affects Kernel versions < 0e21e6cd5eebfc929ac5fa3b97ca2d4ace3cb6a3. 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 Linux Kernel, which is a critical component of the Linux operating system. The Linux Kernel is responsible for managing system resources and providing an interface between the hardware and software layers. 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. The function is responsible for rebalancing the child nodes of a B-tree data structure when a node is removed. However, due to a programming error, a use-after-free vulnerability exists in this function.

Vulnerability Detail

The use-after-free vulnerability in dm btree remove can be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. When a node is removed from the B-tree, the rebalance_children() function attempts to rebalance the remaining child nodes. However, if the function encounters an error during the rebalancing process, it may incorrectly free memory that is still being used. This can lead to a situation where a dangling pointer exists, and an attacker can manipulate the freed memory to execute malicious code or crash the system. The impact of this vulnerability depends on the attacker's ability to control the freed memory and the context in which the vulnerability is exploited.

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 known workaround for this vulnerability. It is recommended to apply the official patch or update the Linux Kernel to the latest version.

Conclusion

The use-after-free vulnerability in dm btree remove is a critical security issue that affects the Linux Kernel. It can be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. It is recommended to update the Linux Kernel to the latest version or apply the official patch to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the attacker's ability to exploit the use-after-free condition. It could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.

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 to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities are present.

No, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the latest version or apply the official patch.

Yes, this vulnerability can be exploited remotely if the attacker can send malicious input to the affected system.

Yes, this vulnerability has been fixed in Linux Kernel version v5.10.88 by commit 0e21e6cd5eebfc929ac5fa3b97ca2d4ace3cb6a3.

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