CVE-2023-53346: kernel/fail_function: fix memory leak with using debugfs_lookup()
In the Linux kernel, the following vulnerability has been resolved:
kernel/fail_function: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it,
otherwise the memory will leak over time. To make things simpler, just
call debugfs_lookup_and_remove() instead which handles all of the logic
at once.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53346 is a Linux kernel memory leak in fail_function debugfs cleanup. A local low-privileged user could contribute to resource exhaustion, affecting availability rather than data theft or integrity. The source bundle rates it medium with CVSS 5.5.
Executive priority
Treat as a moderate availability risk. Prioritize routine kernel patching, with faster handling for multi-user servers, shared hosting, build runners, and other systems where untrusted local users may run code.
Technical view
The issue is CWE-401: debugfs_lookup() returned a reference that was not released with dput(), causing memory to leak over time. The kernel fix replaces the pattern with debugfs_lookup_and_remove(), which handles lookup and removal cleanup together.
Likely exposure
Exposure is limited to systems running affected Linux kernel builds. The source bundle references versions around 4.16 through 6.3 and stable fix commits, but distro-specific affected and fixed package versions are not provided.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact. KEV is false, and the provided sources do not report active exploitation or public weaponization.
Researcher notes
The evidence supports a local availability issue from a debugfs reference leak. Exact affected ranges and distro package fixes are incomplete in the bundle, so validation should rely on vendor kernel advisories and commit lineage.
Mitigation direction
Apply the relevant Linux stable kernel fix or vendor kernel update.
Check distro advisories for backported fixed package versions.
Prioritize shared systems where low-privileged local users exist.
Reboot into the fixed kernel after update, if required.
Monitor kernel memory pressure until remediation is complete.
Validation and detection
Inventory running kernel versions across Linux hosts.
Map each kernel to vendor advisories or the referenced stable commits.
Confirm updated systems booted into the fixed kernel.
Review local-user multi-tenant systems first.
Check monitoring for unexplained memory growth or availability impact.
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.