CVE-2023-53396
published 2025-09-18CVE-2023-53396: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
3.6th percentile
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
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 < 9f565752b328fe53c9e42b7d4e4d89a1da63d738 | 9f565752b328fe53c9e42b7d4e4d89a1da63d738 |
| linux | linux | >= 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 < 7e264f67b7d6580eff5c2696961039fd05c69258 | 7e264f67b7d6580eff5c2696961039fd05c69258 |
| linux | linux | >= 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 < 517ddc0259d7a7231486bdafde8035c478bc4088 | 517ddc0259d7a7231486bdafde8035c478bc4088 |
| linux | linux | >= 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 < 3a36d20e012903f45714df2731261fdefac900cb | 3a36d20e012903f45714df2731261fdefac900cb |
| linux | linux | >= 5.15.33 < 5.15.112 | 5.15.112 |
| linux | linux | >= 5.16.19 < 5.17 | 5.17 |
| linux | linux | >= 5.17.2 < 5.18 | 5.18 |
| linux | linux | >= c67bc98d1f0853bb196e9c48eab38b6f2ddab795 < 43b2f7d690697182beed6f71aa57b7249d3cfc9c | 43b2f7d690697182beed6f71aa57b7249d3cfc9c |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 5.15.33 < 5.15.112 | 5.15.112 |
| linux | linux_kernel | >= 5.16.19 < 5.17 | 5.17 |
| linux | linux_kernel | >= 5.17.2 < 6.1.28 | 6.1.28 |
| linux | linux_kernel | >= 6.2 < 6.2.15 | 6.2.15 |
| linux | linux_kernel | >= 6.3 < 6.3.2 | 6.3.2 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2023-53396: 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,
osv·2025-09-18·CVSS 5.5
CVE-2023-53396 [MEDIUM] CVE-2023-53396: 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,
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.
GHSA
GHSA-427x-59vx-vjwq: 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
ghsa_unreviewed·2025-09-18
CVE-2023-53396 [MEDIUM] CWE-401 GHSA-427x-59vx-vjwq: 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
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.
Red Hat
kernel: Linux kernel: Memory leak leading to denial of service via renaming a file in an encrypted directory
vendor_redhat·2025-09-18·CVSS 5.5
CVE-2023-53396 [MEDIUM] CWE-772 kernel: Linux kernel: Memory leak leading to denial of service via renaming a file in an encrypted directory
kernel: Linux kernel: Memory leak leading to denial of service via renaming a file in an encrypted directory
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_rena
Debian
CVE-2023-53396: linux - In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix ...
vendor_debian·2023·CVSS 5.5
CVE-2023-53396 [MEDIUM] CVE-2023-53396: linux - In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix ...
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.
Scope: local
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/3a36d20e012903f45714df2731261fdefac900cbhttps://git.kernel.org/stable/c/43b2f7d690697182beed6f71aa57b7249d3cfc9chttps://git.kernel.org/stable/c/517ddc0259d7a7231486bdafde8035c478bc4088https://git.kernel.org/stable/c/7e264f67b7d6580eff5c2696961039fd05c69258https://git.kernel.org/stable/c/9f565752b328fe53c9e42b7d4e4d89a1da63d738
2025-09-18
Published