CVE-2023-53276: ubifs: Free memory for tmpfile name
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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53276 is a Linux kernel memory leak in UBIFS when temporary files are opened in encrypted directories. A local user could repeatedly trigger the leak and reduce system memory, potentially causing availability impact. This is not a remote takeover issue, and the provided sources do not show active exploitation.
Executive priority
Treat as routine-to-priority patching for affected Linux/UBIFS environments. Business risk is service disruption from memory exhaustion, not data theft or remote compromise. Prioritize embedded, appliance, or flash-storage systems using UBIFS, especially where untrusted local users or workloads exist.
Technical view
UBIFS tmpfile handling calls fscrypt_setup_filename for encrypted directories and fails to free allocated filename memory after copying it into the directory entry inode. The CVE maps to CWE-401 and CVSS 5.5, with local, low-privilege, no-user-interaction characteristics and high availability impact.
Likely exposure
Exposure is most likely on Linux systems using UBIFS with encrypted directories where local users or workloads can create temporary files. Many general-purpose servers may not use UBIFS. Confirm kernel version, UBIFS usage, filesystem encryption, and whether vendor kernels include the referenced stable fixes.
Exploitation context
The source describes a memory leak observed by kmemleak during tmpfile creation. Exploitation would require local ability to trigger the affected file operation. CISA KEV is false in the provided data, and no cited source reports active exploitation.
Researcher notes
The issue is a missing free in ubifs_tmpfile after fscrypt_setup_filename allocation. The record identifies the original affected lineage and multiple stable commit references. The affected-version data is not enough alone to determine every distribution kernel status; vendor backport verification is required.
Mitigation direction
Apply Linux kernel updates containing the referenced UBIFS stable fixes.
If using a vendor kernel, follow the vendor advisory and backport status.
Prioritize systems using UBIFS with encrypted directories and local multi-user access.
If patching is delayed, reduce unnecessary local access to affected systems.
Validation and detection
Inventory Linux kernel versions across managed systems.
Identify systems with UBIFS enabled or mounted.
Check whether encrypted UBIFS directories are in use.
Verify installed kernels include one of the referenced stable commits or vendor backports.
Monitor memory pressure on suspected affected systems until patched.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.