Vulnerability in dm package: Null Pointer Race when Completing IO

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001910: dm: fix mempool NULL pointer race when completing IO. Affects Kernel versions < 6e506f07c5b561d673dd0b0d8f7f420cc48024fb. 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 package is a component of the Linux Kernel that provides device-mapper functionality. It allows for the creation of virtual block devices that can perform various operations on data passing through them. The package is widely used in Linux-based systems and is responsible for managing I/O operations. However, a vulnerability has been discovered in the dm package that can lead to a null pointer race when completing IO operations.

Vulnerability Detail

The vulnerability in the dm package arises due to a race condition involving a null pointer. When completing IO operations, there is a possibility of a race condition occurring, where a null pointer is accessed before it is properly initialized. This can result in a system crash or potential privilege escalation for an attacker who can exploit this vulnerability. The impact and attack plausibility of this vulnerability have not been proven yet.

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. It is advised to apply the fix by updating the Linux Kernel to the recommended version.

Conclusion

The vulnerability in the dm package that causes a null pointer race when completing IO operations can be mitigated by updating the Linux Kernel to version v5.14.14 or later. This fix addresses the race condition and ensures the stability and security of the system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The dm package is a component of the Linux Kernel that provides device-mapper functionality. It allows for the creation of virtual block devices that can perform various operations on data passing through them.

A null pointer race is a type of race condition where a null pointer is accessed before it is properly initialized. This can lead to unexpected behavior, crashes, or potential security vulnerabilities.

The potential ramifications of this vulnerability include system crashes and potential privilege escalation for attackers who can exploit the null pointer race condition.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.14 or later, which includes the necessary fix for the null pointer race condition.

No specific workaround is mentioned for this vulnerability. It is advised to apply the fix by updating the Linux Kernel to the recommended version.

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