CVE-2023-52936: kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
In the Linux kernel, the following vulnerability has been resolved:
kernel/irq/irqdomain.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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in irqdomain debugfs cleanup. A local low-privileged user could potentially cause memory to leak over time, creating availability risk. The cited impact is denial of service, not data theft or tampering.
Executive priority
Treat as routine but real availability risk. Prioritize internet-facing infrastructure only if local users or workloads can obtain shell or container-level access; otherwise schedule through normal kernel patch cycles.
Technical view
irqdomain.c used debugfs_lookup() without releasing the returned dentry with dput(). The fix replaces that pattern with debugfs_lookup_and_remove(), which performs lookup and removal cleanup together. CVSS is 5.5 with local access, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds. The bundle lists Linux kernel versions and stable fix commits, but exact downstream distribution package status must be confirmed with vendor advisories or backport notes.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The CVSS vector indicates local access with low privileges is required. The main risk is resource exhaustion through a memory leak, not confidentiality or integrity compromise.
Researcher notes
Evidence supports CWE-401 memory leak in kernel irqdomain debugfs cleanup. The bundle provides stable commit references but not exploit reports, detailed affected range semantics, or distribution-specific package names. Avoid assuming all Linux versions are affected.
Mitigation direction
Update to a kernel build containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes.
Prioritize shared systems with untrusted local users.
Monitor vendor kernel packages until fixed builds are installed.
Validation and detection
Inventory Linux kernel versions across affected assets.
Compare installed kernels with vendor fixed package lists.
Confirm whether referenced stable commits are present or backported.
Review host telemetry for abnormal memory growth symptoms.
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.