CVE-2023-53197: USB: uhci: fix memory leak with using debugfs_lookup()
In the Linux kernel, the following vulnerability has been resolved:
USB: uhci: 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 Linux kernel issue is a resource leak in the USB UHCI driver cleanup path. A kernel debug filesystem lookup was not released correctly, so memory could leak over time. The source bundle does not provide CVSS, business impact, attack prerequisites, or evidence of exploitation.
Executive priority
Treat as routine kernel hygiene unless your environment depends heavily on affected Linux kernels with USB/UHCI exposure. There is no supplied evidence of active exploitation or severe impact, but unbounded kernel memory leaks can affect stability over time.
Technical view
The resolved bug changes UHCI debugfs removal logic from debugfs_lookup() without dput() to debugfs_lookup_and_remove(), preventing a reference leak. The listed affected Linux versions include 5.13, 5.15.100, 6.1.18, 6.2.5, and 6.3, with fixes referenced in Linux stable commits.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the relevant USB UHCI/debugfs code path present. The bundle does not state whether local access, USB hardware, debugfs mounting, or privileges are required to trigger the leak.
Exploitation context
The CVE is not marked KEV, and the supplied sources do not cite active exploitation or public exploit activity. The documented issue is memory leakage over time, but attacker control and practical exploitability are not established in the bundle.
Researcher notes
The evidence supports a missing reference release after debugfs_lookup() in the UHCI driver. The bundle lacks CVSS, CWE, trigger conditions, privilege requirements, and distro-specific fixed versions. Avoid assuming denial-of-service exploitability without additional vendor or kernel analysis.
Mitigation direction
Inventory Linux systems for the affected kernel versions listed in the CVE record.
Update to a vendor or Linux stable kernel containing the referenced fix commits.
Use distribution advisories or backport notes to confirm fixed package versions.
Prioritize systems with USB/UHCI support and debugfs enabled until exposure is clearer.
Monitor kernel memory behavior on potentially affected systems before maintenance windows.
Validation and detection
Compare running kernel versions against vendor advisories for CVE-2023-53197.
Verify whether your kernel includes one of the referenced stable commits.
For source builds, confirm UHCI cleanup uses debugfs_lookup_and_remove() or releases lookup references.
Check asset inventory for Linux 5.13, 5.15.100, 6.1.18, 6.2.5, and 6.3.
Confirm no exception leaves affected kernels unpatched in production images.
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-53197 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:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.