CVE-2023-53391: shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs
In the Linux kernel, the following vulnerability has been resolved:
shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs
As the ramfs-based tmpfs uses ramfs_init_fs_context() for the
init_fs_context method, which allocates fc->s_fs_info, use ramfs_kill_sb()
to free it and avoid a memory leak.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53391 is a Linux kernel memory leak in ramfs-based tmpfs cleanup. A local low-privileged user may be able to trigger repeated leaks, creating an availability risk. The cited record rates it medium, with high availability impact and no confidentiality or integrity impact.
Executive priority
Treat this as a routine but real availability issue. It does not indicate remote compromise or data exposure from the supplied evidence, but affected shared Linux systems should be patched through normal kernel maintenance because local users can potentially degrade service availability.
Technical view
The bug is in shmem/tmpfs superblock teardown: ramfs-based tmpfs used ramfs_init_fs_context(), which allocates fc->s_fs_info, but did not use ramfs_kill_sb() to free it. The fix changes the kill_sb method to ramfs_kill_sb(). CVSS is 5.5: local, low complexity, low privileges, no user interaction, availability high.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions listed in the CVE data, including lines around 5.10.188, 5.15.121, 6.1.39, 6.4.4, and 6.5. Distribution backports may change practical exposure, so package-level vendor status must be checked.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates local access with low privileges is required. Impact is denial of service through resource exhaustion, not data theft or code execution.
Researcher notes
The key evidence is the kernel fix rationale: ramfs_init_fs_context() allocates s_fs_info, and ramfs_kill_sb() is needed to release it. The source bundle does not provide a reproducer, exploit report, CWE mapping, or distribution-specific fixed package versions.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixed packages.
Prioritize shared or multi-user Linux systems if affected.
Apply normal reboot or live-patching procedures after kernel update.
Monitor memory pressure until affected systems are patched.
Validation and detection
Inventory kernel versions across Linux assets.
Compare running kernels against vendor advisories and the CVE affected data.
Confirm the ramfs_kill_sb() fix is present in deployed kernel sources or changelogs.
Verify patched systems boot into the expected fixed kernel.
Review monitoring for unexplained kernel memory growth on affected hosts.
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.
cve · low confidence lookup
CVE-2023-53391 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.