Service interruption via unreleased tmpfile name buffers
Published Sep 16, 2025 · Updated Sep 16, 2025
Memory leak in UBIFS in affected Linux kernel branches beginning with 4.10 allows local users to exhaust kernel memory via tmpfiles. The ubifs_tmpfile path calls fscrypt_setup_filename for a directory-entry name but fails to call fscrypt_free_filename after copying it into the inode. The path requires permission to create temporary files in an encrypted UBIFS directory; repeated calls retain allocations and can interrupt service.
Summary
What happened
Memory leak in UBIFS in affected Linux kernel branches beginning with 4.10 allows local users to exhaust kernel memory via tmpfiles. The ubifs_tmpfile path calls fscrypt_setup_filename for a directory-entry name but fails to call fscrypt_free_filename after copying it into the inode. The path requires permission to create temporary files in an encrypted UBIFS directory; repeated calls retain allocations and can interrupt service.
The record
- CVE
- CVE-2023-53276
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <107d481642c356a5668058066360fc473911e628
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1e43d4284bdc3bd34bd770fea13910ac37ab0618
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29738e1bcc799dd754711d4e4aab967f0c018175
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <823f554747f8aafaa965fb2f3ae794110ed429ef
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8ad8c67a897e68426e85990ebfe0a7d1f71fc79f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ce840284929b75dbbf062e0ce7fcb78a63b08b5e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd197308c0e4f738c7ea687d5332035c5753881c
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo