Vulnerability in Kernel: dm btree remove

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001388: dm btree remove: assign new_root only when removal succeeds. Affects Kernel versions < 8fbae4a1bdb5b889490cdee929e68540151536e5. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a crucial component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The dm btree remove vulnerability affects the Kernel, specifically the dm btree module. This module is responsible for managing the B-tree data structure used by the device mapper subsystem. The vulnerability arises from an incorrect assignment of the new root during the removal process. This vulnerability could potentially be exploited by an attacker to manipulate the B-tree structure and cause system instability or unauthorized access.

Vulnerability Detail

The dm btree remove vulnerability occurs when the new root is assigned before ensuring the successful removal of a node from the B-tree structure. This can lead to inconsistencies in the B-tree, potentially resulting in system instability or unauthorized access. The vulnerability has been identified and fixed in Linux Kernel version v4.19.198 by commit 8fbae4a1bdb5b889490cdee929e68540151536e5.

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 essential to update the Kernel to the fixed version as soon as possible.

Conclusion

The dm btree remove vulnerability in the Kernel's dm btree module can lead to system instability or unauthorized access. It is crucial to update the Kernel to the fixed version (v4.19.198 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 dm btree remove vulnerability can potentially lead to system instability or unauthorized access. Exploiting this vulnerability, an attacker could manipulate the B-tree structure and cause disruption or gain unauthorized control over the system.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

At the time of this report, there is no known exploit for the dm btree remove vulnerability. However, it is crucial to update the Kernel to the fixed version to mitigate any potential risks.

This vulnerability requires local access to the system to exploit. However, if an attacker gains local access, they could potentially exploit the vulnerability to manipulate the B-tree structure and compromise the system.

The recommended solution is to update the Kernel to the fixed version. However, if updating is not feasible, implementing additional security measures such as restricting local access and monitoring system logs for suspicious activities can help mitigate the risk to some extent.

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