Vulnerability in Kernel: md: Don't set mddev private to NULL in raid0 pers->free
Summary
GSD-2022-1003006: md: Don't set mddev private to NULL in raid0 pers->free. Affects Kernel versions >= 0c031fd37f69deb0cd8c43bbfcfccd62ebd7e952, < b7a51df785031cc49caf1c59766ca89cfa97b54b. 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 Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. One of the features of the Kernel is the ability to create and manage RAID arrays, which improve data redundancy and performance. However, a vulnerability has been discovered in the Kernel's RAID0 (striping) implementation that can lead to potential security issues.
Vulnerability Detail
The vulnerability arises from a flaw in the RAID0 (striping) implementation of the Kernel's md (multiple devices) subsystem. Specifically, in the raid0 personality's free function, the mddev private field is set to NULL. This can result in a use-after-free vulnerability, where a reference to the freed memory can still be accessed, potentially leading to a crash or arbitrary code execution. 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
No specific workaround has been mentioned for this vulnerability.
Conclusion
In conclusion, a vulnerability has been identified in the Kernel's RAID0 implementation that can result in a use-after-free issue. It is recommended to update the Kernel to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to lead to a crash or arbitrary code execution.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Kernel to the latest version that includes the fix for this vulnerability.
You can find more information about this vulnerability in the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003006.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
