Fix firmware activation deadlock scenarios in Kernel
Summary
GSD-2022-1003587: nvdimm: Fix firmware activation deadlock scenarios. Affects Kernel versions >= 48001ea50d17f3eb06a552e9ecf21f7fc01b25da, < 641649f31e20df630310f5c22f26c071acc676d4. 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 acts as a bridge between hardware and software. It provides essential functionalities and services to enable the proper functioning of the system. The vulnerability described here affects the Kernel's nvdimm module, which is responsible for managing non-volatile memory devices. Non-volatile Dual In-line Memory Modules (NVDIMMs) combine the speed of DRAM with the persistence of storage, making them valuable for applications requiring fast and durable memory. However, a deadlock scenario can occur during firmware activation, leading to potential security vulnerabilities.
Vulnerability Detail
The vulnerability arises from a deadlock scenario that can occur during firmware activation in the nvdimm module of the Kernel. This deadlock can potentially be exploited by attackers to gain unauthorized access or disrupt the system. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Kernel version v5.9 and is fixed in version v5.10.121. The fix can be found in commit 641649f31e20df630310f5c22f26c071acc676d4. For more details, refer to the provided references.
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 vulnerability in the Kernel's nvdimm module, causing a deadlock scenario during firmware activation, can potentially lead to security risks. It is crucial to update the Kernel to version v5.10.121 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The nvdimm module in the Kernel is responsible for managing non-volatile memory devices, such as NVDIMMs. These devices combine the speed of DRAM with the persistence of storage, making them useful for applications requiring fast and durable memory.
A deadlock scenario occurs when two or more processes or threads are unable to proceed because each is waiting for the other to release a resource. In the case of this vulnerability, a deadlock can occur during firmware activation in the nvdimm module.
If exploited, this vulnerability could allow attackers to gain unauthorized access to the system or disrupt its normal operation. However, the actual impact and attack plausibility have not been proven yet.
You can use tools like Vulert to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software, using just a manifest file like package-lock.json. Visit the Vulert playground at Vulert Scanner to check if your application is affected.
For more information about this vulnerability, including technical details and the fix, refer to the provided references.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
