CVE-2023-53276
published 2025-09-16CVE-2023-53276: In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.15%
4.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Free memory for tmpfile name
When opening a ubifs tmpfile on an encrypted directory, function
fscrypt_setup_filename allocates memory for the name that is to be
stored in the directory entry, but after the name has been copied to the
directory entry inode, the memory 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 'tmpfile' just opening a
tmpfile:
unreferenced object 0xffff88810178f380 (size 32):
comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s)
backtrace:
__kmem_cache_alloc_node
__kmalloc
fscrypt_setup_filename
ubifs_tmpfile
vfs_tmpfile
path_openat
Free this memory after it has been copied to the inode.
Affected
23 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 | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 8ad8c67a897e68426e85990ebfe0a7d1f71fc79f | 8ad8c67a897e68426e85990ebfe0a7d1f71fc79f |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 107d481642c356a5668058066360fc473911e628 | 107d481642c356a5668058066360fc473911e628 |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 823f554747f8aafaa965fb2f3ae794110ed429ef | 823f554747f8aafaa965fb2f3ae794110ed429ef |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3 | b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3 |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < ce840284929b75dbbf062e0ce7fcb78a63b08b5e | ce840284929b75dbbf062e0ce7fcb78a63b08b5e |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 29738e1bcc799dd754711d4e4aab967f0c018175 | 29738e1bcc799dd754711d4e4aab967f0c018175 |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < fd197308c0e4f738c7ea687d5332035c5753881c | fd197308c0e4f738c7ea687d5332035c5753881c |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 1e43d4284bdc3bd34bd770fea13910ac37ab0618 | 1e43d4284bdc3bd34bd770fea13910ac37ab0618 |
| linux | linux | >= f4f61d2cc6d8789a52245a4733b3e5643be154f3 < 1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3 | 1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3 |
| linux | linux_kernel | < 4.14.315 | 4.14.315 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| 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 | >= 4.15 < 4.19.283 | 4.19.283 |
| linux | linux_kernel | >= 4.20 < 5.4.243 | 5.4.243 |
| linux | linux_kernel | >= 5.11 < 5.15.111 | 5.15.111 |
| linux | linux_kernel | >= 5.16 < 6.1.28 | 6.1.28 |
| linux | linux_kernel | >= 5.5 < 5.10.180 | 5.10.180 |
| 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-53276: In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted d
osv·2025-09-16·CVSS 5.5
CVE-2023-53276 [MEDIUM] CVE-2023-53276: In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted d
In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory 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 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.
GHSA
GHSA-jfrm-9rr7-r45w: In the Linux kernel, the following vulnerability has been resolved:
ubifs: Free memory for tmpfile name
When opening a ubifs tmpfile on an encrypted
ghsa_unreviewed·2025-09-16
CVE-2023-53276 [MEDIUM] CWE-401 GHSA-jfrm-9rr7-r45w: In the Linux kernel, the following vulnerability has been resolved:
ubifs: Free memory for tmpfile name
When opening a ubifs tmpfile on an encrypted
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Free memory for tmpfile name
When opening a ubifs tmpfile on an encrypted directory, function
fscrypt_setup_filename allocates memory for the name that is to be
stored in the directory entry, but after the name has been copied to the
directory entry inode, the memory 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 'tmpfile' just opening a
tmpfile:
unreferenced object 0xffff88810178f380 (size 32):
comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s)
backtrace:
__kmem_cache_alloc_node
__kmalloc
fscrypt_setup_filename
ubifs_tmpfile
vfs_tmpfile
path_openat
Free this memory after it has been copied to the inode.
Red Hat
kernel: Kernel: Denial of Service via ubifs memory leak
vendor_redhat·2025-09-16·CVSS 5.5
CVE-2023-53276 [MEDIUM] CWE-772 kernel: Kernel: Denial of Service via ubifs memory leak
kernel: Kernel: Denial of Service via ubifs memory leak
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Free memory for tmpfile name
When opening a ubifs tmpfile on an encrypted directory, function
fscrypt_setup_filename allocates memory for the name that is to be
stored in the directory entry, but after the name has been copied to the
directory entry inode, the memory 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 'tmpfile' just opening a
tmpfile:
unreferenced object 0xffff88810178f380 (size 32):
comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s)
backtrace:
__kmem_cache_alloc_node
__kmalloc
fscrypt_setup_filename
ubifs_tmpfile
vfs_tmpfile
path_openat
Free this memory a
Debian
CVE-2023-53276: linux - In the Linux kernel, the following vulnerability has been resolved: ubifs: Free...
vendor_debian·2023·CVSS 5.5
CVE-2023-53276 [MEDIUM] CVE-2023-53276: linux - In the Linux kernel, the following vulnerability has been resolved: ubifs: Free...
In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory 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 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.
Scope: local
bookwo
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/107d481642c356a5668058066360fc473911e628https://git.kernel.org/stable/c/1e43d4284bdc3bd34bd770fea13910ac37ab0618https://git.kernel.org/stable/c/1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3https://git.kernel.org/stable/c/29738e1bcc799dd754711d4e4aab967f0c018175https://git.kernel.org/stable/c/823f554747f8aafaa965fb2f3ae794110ed429efhttps://git.kernel.org/stable/c/8ad8c67a897e68426e85990ebfe0a7d1f71fc79fhttps://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3https://git.kernel.org/stable/c/ce840284929b75dbbf062e0ce7fcb78a63b08b5ehttps://git.kernel.org/stable/c/fd197308c0e4f738c7ea687d5332035c5753881c
2025-09-16
Published