LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
8

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53346 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53346Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4b1a29a7f5425d32640b34b8a755f34e02f64d0f, 4b1a29a7f5425d32640b34b8a755f34e02f64d0f, 4b1a29a7f5425d32640b34b8a755f34e02f64d0f, 4b1a29a7f5425d32640b34b8a755f34e02f64d0f, 4b1a29a7f5425d32640b34b8a755f34e02f64d0f, 4b1a29a7f5425d32640b34b8a755f34e02f64d0funaffected
LinuxLinux4.16, 0, 5.4.235, 5.10.173, 5.15.100, 6.1.18, 6.2.5, 6.3affected
Weakness

CWE details

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.