LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53415: USB: dwc3: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: 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. Note, the root dentry for the debugfs directory for the device needs to be saved so we don't have to keep looking it up, which required a bit more refactoring to properly create and remove it when needed.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the USB DWC3 debugfs cleanup path. The main business risk is local denial of service: repeated triggering could consume memory over time and affect system availability. It is not described as exposing data or allowing remote compromise in the provided sources.

Executive priority

Treat this as a routine but real availability risk for Linux fleets, especially shared systems or appliances with less-trusted local users. It does not justify emergency remote-compromise response based on the supplied evidence, but it should be included in normal kernel patch cycles.

Technical view

The flaw is CWE-401 in Linux USB DWC3 handling: debugfs_lookup() returned a dentry that was not released with dput(). The kernel fix replaces the pattern with debugfs_lookup_and_remove() and refactors storage of the debugfs root dentry. CVSS is 5.5: local attack vector, low privileges, no user interaction, high availability impact.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions or commits that include the vulnerable USB DWC3 debugfs code. The bundle lists Linux as affected across version and commit ranges, including 5.13 through before fixed stable updates. Distro backport status is not provided.

Exploitation context

The CVE is not in KEV, and the supplied sources do not state active exploitation or public exploit availability. The scoring indicates local, low-privileged access is required, with availability as the only stated security impact.

Researcher notes

The key evidence is the kernel change correcting debugfs dentry lifetime handling. Research should focus on confirming affected kernel lineage, vendor backports, and whether target configurations expose the relevant DWC3 debugfs path. Avoid assuming exploitability beyond the local availability impact stated by CVSS.

Mitigation direction

  • Apply a vendor or distribution kernel update containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes to supported kernel packages.
  • Restrict unnecessary local shell access on affected systems until patched.
  • Monitor affected hosts for unexplained memory pressure or availability degradation.
  • Prioritize systems where local users or workloads are less trusted.

Validation and detection

  • Inventory Linux kernel versions on systems using affected release lines.
  • Confirm whether vendor kernels include the referenced stable DWC3 debugfs fix.
  • Review asset exposure for systems with USB DWC3 functionality in use.
  • Check vulnerability management data for CVE-2023-53415 package status.
  • Document any accepted risk where patch availability is not yet confirmed.
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-53415 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-53415Attack 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
LinuxLinux8d396bb0a5b62b326f6be7594d8bd46b088296bd, 8d396bb0a5b62b326f6be7594d8bd46b088296bd, 8d396bb0a5b62b326f6be7594d8bd46b088296bd, 8d396bb0a5b62b326f6be7594d8bd46b088296bd, 3bef21035888dd19750ad79b5d08fe52a02ad719, d7e403eea007f47776186d4d572f234b1221e6e3, e52d43c82f2f6556f0b7a790c19c072c1e99a95f, afd8b0d091d5b4febe2d0ac3b7735c1826329302, 4.19.196, 5.4.128, 5.10.46, 5.12.13unaffected
LinuxLinux5.13, 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.