Use-after-free vulnerability in nvme controller reset during load
Summary
GSD-2022-1000392: nvme: fix a possible use-after-free in controller reset during load. Affects Kernel versions < 0ead57ceb21bbf15963b4874c2ac67143455382f. 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 nvme package is a driver for Non-Volatile Memory Express (NVMe) devices in the Linux Kernel. NVMe is a protocol designed for accessing solid-state drives (SSDs) over a PCI Express (PCIe) bus. The controller reset functionality in the nvme driver is responsible for resetting the NVMe controller during system initialization or error recovery. This vulnerability affects the controller reset process during load, potentially leading to a use-after-free vulnerability.
Vulnerability Detail
The use-after-free vulnerability in the nvme controller reset during load can be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. The vulnerability occurs when the controller reset process incorrectly handles memory deallocation, allowing an attacker to access freed memory and potentially modify its contents. This can lead to various security issues, including privilege escalation or system crashes.
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 →
Conclusion
The use-after-free vulnerability in the nvme controller reset during load can have serious security implications, including arbitrary code execution and denial-of-service. It is crucial to update the Linux Kernel to version v5.10.102 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
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 alert you in real-time if your system is vulnerable.
No, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
Yes, this vulnerability is present in versions of the Linux Kernel prior to v5.10.102.
There is no evidence of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
