CVE-2023-53670
BaseFortify
Publication date: 2025-10-07
Last updated on: 2026-02-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak issue in the Linux kernel's nvme-core component. Specifically, it involves the failure to properly call dev_pm_qos_hide_latency_tolerance() during error handling, which leads to unreferenced memory objects remaining allocated (a memory leak). The fix involves calling this function in the error unwind patch to prevent the leak.
How can this vulnerability impact me? :
The memory leak could cause increased memory usage over time, potentially leading to degraded system performance or instability if the leaked memory accumulates significantly. This could affect systems using the nvme-core driver in the Linux kernel.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by using the Linux kernel's kmemleak tool to scan for memory leaks related to the nvme driver. Suggested commands include: 'kmemleak-clear' to clear previous reports, running the nvme test (e.g., './check nvme/044'), followed by 'kmemleak-scan' to scan for leaks and 'kmemleak-show' to display any unreferenced objects indicating a memory leak.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the nvme-core memory leak issue has been fixed by calling dev_pm_qos_hide_latency_tolerance() in the error unwind patch. Until then, monitoring with kmemleak and avoiding use of vulnerable kernel versions is recommended.