CVE-2023-53412: USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup()
In the Linux kernel, the following vulnerability has been resolved:
USB: gadget: bcm63xx_udc: 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
CVE-2023-53412 is a Linux kernel memory leak in the USB gadget bcm63xx_udc driver. A local, low-privileged user could potentially drive repeated leakage and degrade system availability. The evidence points to an availability issue, not data theft or code execution.
Executive priority
Handle through normal vulnerability management unless exposed systems are operationally critical or hard to reboot. The main business risk is local denial of service on affected Linux deployments, especially embedded or appliance environments using this USB gadget driver.
Technical view
The issue is CWE-401: debugfs_lookup() was used without releasing the returned object with dput(). The kernel 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 ranges that include and use the bcm63xx_udc USB gadget driver. The bundle does not identify affected distributions, appliance models, or cloud services. Treat downstream vendor kernel advisories as authoritative for package-level exposure.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. Exploitation would require local access and low privileges. The described impact is resource exhaustion over time through a memory leak, not confidentiality or integrity compromise.
Researcher notes
Evidence is narrow and kernel-specific. The public record provides the memory-leak root cause, CVSS vector, affected upstream ranges, and stable commit references. It does not provide exploit reports, downstream distribution mappings, or named non-upgrade mitigations.
Mitigation direction
Apply a vendor or distribution kernel update containing the referenced stable fixes.
Check Linux kernel and downstream vendor advisories for your exact branch.
Prioritize systems where bcm63xx_udc or USB gadget functionality is enabled.
If updates are unavailable, ask the vendor for supported compensating controls.
Validation and detection
Inventory Linux kernel versions and downstream package build identifiers.
Confirm whether the bcm63xx_udc driver is present or enabled in relevant builds.
Map deployed kernels against the affected and fixed upstream ranges.
Verify patched systems include one of the referenced stable commits.
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.