Vulnerability in dm package: Null Pointer Race when Completing IO
Summary
GSD-2021-1002078: dm: fix mempool NULL pointer race when completing IO. Affects Kernel versions < 6e506f07c5b561d673dd0b0d8f7f420cc48024fb. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
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 by mapping physical block devices onto them. This package is widely used in Linux-based systems and is responsible for managing I/O operations.
The vulnerability identified in the dm package involves a null pointer race condition when completing I/O. This race condition can lead to a null pointer dereference, potentially resulting in a system crash or other unpredictable behavior.
Vulnerability Detail
The vulnerability arises due to a race condition in the dm package when completing I/O operations. Under certain circumstances, multiple threads can concurrently access a shared memory pool, leading to a null pointer dereference if the memory pool is deallocated before the completion of I/O operations. An attacker could potentially exploit this vulnerability to crash the system or execute arbitrary code.
This vulnerability has been assigned the ID GSD-2021-1002078 and is fixed in Linux Kernel version v5.14.14 by commit 6e506f07c5b561d673dd0b0d8f7f420cc48024fb.
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
As a temporary workaround, users can disable or avoid using the dm package if it is not essential for their system's functionality. However, this may not be a feasible solution for systems heavily reliant on device-mapper functionality.
Conclusion
The vulnerability in the dm package can lead to a null pointer dereference due to a race condition when completing I/O operations. It is crucial to update the Linux Kernel to version v5.14.14 or later to mitigate this vulnerability. Users can also utilize the Vulert Playground at https://vulert.com/scanner to check if their system is affected by this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a system crash or allow an attacker to execute arbitrary code.
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 vulnerabilities, including this one, are found.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the fix promptly to mitigate any potential risks.
While updating the Linux Kernel is the recommended solution, you can temporarily disable or avoid using the dm package if it is not critical for your system's operation. However, this may not be a viable long-term solution.
You can refer to the vulnerability details in the GSD Database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/GSD-2021-1002078.json for more information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
