CVE-2023-53346
BaseFortify
Publication date: 2025-09-17
Last updated on: 2025-12-11
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.4.235 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.173 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.100 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.18 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.5 (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 in the Linux kernel involves a memory leak caused by improper handling of the debugfs_lookup() function. When debugfs_lookup() is called, the result must be released with dput() to avoid leaking memory over time. The fix involves using debugfs_lookup_and_remove(), which manages this process correctly and prevents the memory leak.
How can this vulnerability impact me? :
The memory leak caused by this vulnerability can lead to increased memory usage over time, potentially degrading system performance or causing 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 where the vulnerability is fixed by ensuring that debugfs_lookup() calls are replaced with debugfs_lookup_and_remove(), which properly handles memory management and prevents the memory leak.