CVE-2023-53202: PM: domains: fix memory leak with using debugfs_lookup()
In the Linux kernel, the following vulnerability has been resolved:
PM: domains: 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 CVE describes a Linux kernel memory leak in power-management domain debugfs cleanup. It may slowly consume kernel memory over time. The public bundle provides no CVSS score, no CISA KEV listing, and no active-exploitation evidence, so urgency depends on whether affected kernels are deployed.
Executive priority
Handle through normal kernel patch management unless critical assets run affected long-lived kernels. There is no source-backed evidence of active exploitation or severe impact, but kernel memory leaks can affect availability if left unpatched over time.
Technical view
The issue is missing dput() handling after debugfs_lookup() in Linux PM domains code. The kernel fix replaces the pattern with debugfs_lookup_and_remove(), which performs lookup and removal cleanup together. The source bundle names Linux kernel versions and stable commits, but gives no exploitation details or severity score.
Likely exposure
Potential exposure is Linux systems running affected kernel versions or descendants before the referenced stable fixes. The bundle lists Linux kernel 5.11, 5.15.99, 6.1.16, 6.2.3, and 6.3 context, but precise downstream distribution impact must be verified with vendor kernel advisories.
Exploitation context
The provided sources describe a memory leak over time, not a public exploit path. CISA KEV is false in the bundle, and no cited source states active exploitation. Treat exploitability and impact as incomplete until vendor advisories or kernel maintainers provide more detail.
Researcher notes
Focus validation on the PM domains debugfs cleanup path and whether downstream kernels carry the stable commits. The source bundle does not provide CVSS, CWE, exploit prerequisites, reachable configurations, or distribution-specific package names, so avoid broader claims without additional vendor evidence.
Mitigation direction
Check Linux distribution security advisories for CVE-2023-53202 applicability.
Update kernels to versions containing the referenced stable fixes.
Prioritize systems with long uptimes or constrained memory.
Track vendor backports because distribution kernel versions may not match upstream numbering.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Compare deployed kernels against vendor advisories for CVE-2023-53202.
Confirm whether referenced upstream stable commits are included or backported.
Monitor kernel memory trends on potentially affected long-running systems.
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-53202 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Sep 15, 2025, 14:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.