CVEvulnerability
CVE-2023-53396
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2025-09-18
- Last modified
- 2026-06-17
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-401
Description
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Fix memory leak in do_rename
If renaming a file in an encrypted directory, function
fscrypt_setup_filename allocates memory for a file name. This name is
never used, and before returning to the caller the memory for it is not
freed.
When running kmemleak on it we see that it is registered as a leak. The
report below is triggered by a simple program 'rename' that renames a
file in an encrypted directory:
unreferenced object 0xffff888101502840 (size 32):
comm "rename", pid 9404, jiffies 4302582475 (age 435.735s)
backtrace:
__kmem_cache_alloc_node
__kmalloc
fscrypt_setup_filename
do_rename
ubifs_rename
vfs_rename
do_renameat2
To fix this we can remove the call to fscrypt_setup_filename as it's not
needed.
Affected configurations
• linux linux kernel (>= 5.15.33 < 5.15.112)
• linux linux kernel (>= 5.16.19 < 5.17)
• linux linux kernel (>= 5.17.2 < 6.1.28)
• linux linux kernel (>= 6.2 < 6.2.15)
• linux linux kernel (>= 6.3 < 6.3.2)
Related
Weakness · CWE (1)
- CWE-401 Missing Release of Memory after Effective Lifetime weakness
References
- https://git.kernel.org/stable/c/3a36d20e012903f45714df2731261fdefac900cb Patch
- https://git.kernel.org/stable/c/43b2f7d690697182beed6f71aa57b7249d3cfc9c Patch
- https://git.kernel.org/stable/c/517ddc0259d7a7231486bdafde8035c478bc4088 Patch
- https://git.kernel.org/stable/c/7e264f67b7d6580eff5c2696961039fd05c69258 Patch
- https://git.kernel.org/stable/c/9f565752b328fe53c9e42b7d4e4d89a1da63d738 Patch