Vulnerability in Kernel: dm btree remove

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001287: dm btree remove: assign new_root only when removal succeeds. Affects Kernel versions < ba47e65a5de3e0e8270301a409fc63d3129fdb9e. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It manages system resources, facilitates communication between processes, and enables device drivers to interact with hardware. The dm btree remove vulnerability affects the Kernel, specifically the dm (device-mapper) module responsible for managing block devices. This vulnerability arises from an incorrect assignment of the new_root variable during the removal process in the dm btree module.

Vulnerability Detail

The dm btree remove vulnerability occurs when the new_root variable is assigned even if the removal process fails. This can lead to an inconsistent state in the btree structure, potentially causing data corruption or system crashes. Attackers may exploit this vulnerability to manipulate the btree structure, resulting in denial of service or unauthorized access to sensitive information. The vulnerability has been fixed in Linux Kernel version v5.10.51 by commit ba47e65a5de3e0e8270301a409fc63d3129fdb9e.

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.10.51 or later. This can be done by downloading the latest stable version of the Kernel from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. Alternatively, users can rely on package managers or system update mechanisms to automatically install the updated Kernel version.

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 essential to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

The dm btree remove vulnerability in the Kernel can lead to data corruption, system crashes, and potential unauthorized access. It is crucial to update the Linux Kernel to version v5.10.51 or later 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 vulnerability can result in data corruption, system crashes, denial of service, or unauthorized access to sensitive information.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

No, the vulnerability is fixed in Linux Kernel version v5.10.51 and later. Earlier versions may still be vulnerable.

No, this vulnerability requires local access to the system.

There is no known evidence of active exploitation of this vulnerability at the moment.

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.10.51 or later. This can be done by downloading the latest stable version of the Kernel from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided. Alternatively, users can rely on package managers or system update mechanisms to automatically install the updated Kernel version.

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.