Linux kernel
cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*, +4 more
A memory leak vulnerability has been identified in the NVMe core of the Linux kernel. This issue arises during the initialization of NVMe controllers, where user-defined latency tolerances are not properly managed, leading to unreferenced objects that can accumulate over time. The vulnerability has been addressed by modifying the error handling process to include a call that properly hides these latency tolerances, thereby preventing the memory leak.
Exploitation of this vulnerability can lead to a memory leak, where unreferenced objects are not properly cleaned up, potentially causing increased memory usage and degradation of system performance over time.
The vulnerability can be reproduced by using the 'blktests' framework, specifically the 'nvme/044' test, which checks bi-directional authentication. Before running the test, the 'kmemleak' feature should be cleared to prepare for memory leak detection. After the test is executed, 'kmemleak-scan' should be run to scan for memory leaks, followed by 'kmemleak-show' to display any unreferenced objects. The output will reveal the details of the memory leak, including the size of the unreferenced object and its age, indicating that the memory leak has occurred.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for downloading the patched version can be found in the Linux kernel documentation.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.