CVE-2023-53202
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-03
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.11 (inc) 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
How can this vulnerability impact me? :
The memory leak caused by improper handling of debugfs_lookup() results can lead to increased memory usage over time, potentially degrading system performance or causing instability in the Linux kernel environment.
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 result must be properly released by calling dput() to avoid leaking memory over time. The fix involves using debugfs_lookup_and_remove() instead, which handles the necessary logic to prevent the memory leak.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix is applied. The fix involves ensuring that debugfs_lookup() results have dput() called on them to prevent memory leaks, or using debugfs_lookup_and_remove() which handles this automatically.