CVE-2023-53396
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 | From 5.15.33 (inc) to 5.15.112 (exc) |
| linux | linux_kernel | From 5.16.19 (inc) to 5.17 (exc) |
| linux | linux_kernel | From 5.17.2 (inc) to 6.1.28 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.2.15 (exc) |
| linux | linux_kernel | From 6.3 (inc) to 6.3.2 (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's ubifs subsystem when renaming a file in an encrypted directory. Specifically, the function fscrypt_setup_filename allocates memory for a file name but never uses or frees it, causing a memory leak.
How can this vulnerability impact me? :
The impact of this vulnerability is a memory leak that can cause increased memory usage over time when renaming files in encrypted directories. This could potentially degrade system performance or stability if the leak accumulates.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running kmemleak on the system. The memory leak is registered by kmemleak when a file is renamed in an encrypted directory. You can use the kmemleak tool to scan for unreferenced memory objects related to the rename operation. For example, running a simple rename command on a file in an encrypted directory and then checking kmemleak reports can help detect this issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that removes the unnecessary call to fscrypt_setup_filename in the Linux kernel's ubifs rename function. Until the patch is applied, avoid renaming files in encrypted directories to prevent triggering the memory leak.