LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53402: kernel/printk/index.c: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: kernel/printk/index.c: 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-53402 is a Linux kernel memory leak in printk debugfs cleanup logic. A local, low-privileged user could potentially contribute to memory exhaustion, affecting system availability. The source bundle does not show data theft, integrity impact, or remote exploitation.

Executive priority

Treat as scheduled remediation, not emergency response, unless exposed systems allow many untrusted local users. The main business risk is service disruption from memory exhaustion, not confidentiality loss or remote compromise.

Technical view

The flaw is CWE-401 in kernel/printk/index.c. debugfs_lookup() returned a reference that was not released with dput(), leaking memory over time. The kernel fix replaces the pattern with debugfs_lookup_and_remove(), which handles lookup, removal, and reference cleanup.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions listed in the source bundle, including 5.15, 5.15.100, 6.1.18, 6.2.5, and 6.3 entries. Distro backports may change exact status, so kernel package advisories matter.

Exploitation context

The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact only. The bundle says KEV is false and provides no cited evidence of active exploitation or public weaponization.

Researcher notes

The source evidence is concise and code-focused. It identifies the missing dput() after debugfs_lookup() and the stable fix approach, but does not document a concrete trigger path, affected distributions, or exploitation in the wild.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Check vendor advisories for backported fixes in supported distro kernels.
  • Prioritize multi-user systems where untrusted local users have shell or workload access.
  • Monitor systems for abnormal memory pressure until patched.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare kernel builds against vendor fixed versions or linked stable commits.
  • Review package changelogs for the printk debugfs memory leak fix.
  • Confirm no affected kernels remain on high-risk multi-user systems.
Prepared
Confidence
medium
Sources
6

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-53402 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
5Source 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-53402Attack 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
LinuxLinux337015573718b161891a3473d25f59273f2e626b, 337015573718b161891a3473d25f59273f2e626b, 337015573718b161891a3473d25f59273f2e626b, 337015573718b161891a3473d25f59273f2e626bunaffected
LinuxLinux5.15, 0, 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.