Vulnerability in dm btree remove in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001425: dm btree remove: assign new_root only when removal succeeds. Affects Kernel versions < 73f27adaa73e3057a9ec464e33c4f54d34ea5de3. 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. The dm btree remove function is a part of the Kernel's device mapper subsystem, which provides a framework for creating virtual block devices. This vulnerability specifically affects the dm btree remove function, which is responsible for removing entries from a B-tree data structure. The vulnerability arises from the incorrect assignment of the new_root variable, which should only occur if the removal operation succeeds.

Vulnerability Detail

The vulnerability in dm btree remove allows an attacker to potentially manipulate the B-tree data structure, leading to various security risks. By exploiting this vulnerability, an attacker could cause data corruption, trigger a denial-of-service condition, or potentially execute arbitrary code within the Kernel's context. The impact and attack plausibility of this vulnerability have not been proven yet, but it is essential to address it to ensure the integrity and security of 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

There is no specific workaround mentioned for this vulnerability. The recommended approach is to update the Kernel to the patched version as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in dm btree remove in the Kernel can lead to various security risks, including data corruption and potential code execution. It is crucial to update the Kernel to the patched version 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 range from data corruption to potential code execution within the Kernel's context.

By manipulating the B-tree data structure, an attacker can potentially cause data corruption, trigger a denial-of-service condition, or execute arbitrary code within the Kernel's context.

No, the impact and attack plausibility of this vulnerability have not been proven yet. However, it is crucial to address it to ensure system integrity and security.

The recommended solution is to update the Linux Kernel to version v4.14.240 or later, which includes the fix for this vulnerability.

No specific workaround has been mentioned for this vulnerability. Updating the Kernel to the patched version is the recommended approach.

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