CVE-2023-53403
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | to 5.15.99 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.16 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.3 (exc) |
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 in the Linux kernel related to the use of the debugfs_lookup() function. When debugfs_lookup() is called, the returned result must be released by calling dput() to avoid leaking memory. If dput() is not called, memory will leak over time. The fix involves using debugfs_lookup_and_remove(), which handles the necessary logic to prevent the leak.
How can this vulnerability impact me? :
The memory leak caused by improper handling of debugfs_lookup() can lead to increased memory usage over time, potentially degrading system performance or causing system instability if the leak is significant and persistent.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version that includes the fix for the memory leak in debugfs_lookup(), or modify the code to use debugfs_lookup_and_remove() instead of debugfs_lookup() to ensure proper memory management.