CVE-2023-53415

USB: dwc3: fix memory leak with using debugfs_lookup()

MEDIUM
5.5
CVSS Score
Published: September 18, 2025 at 01:58 PM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.19.196v ≥ 5.10.46v ≥ 5.12.13v ≥ 5.4.128v < 5.15.1004.19.196 ≤ v < 4.205.10.46 ≤ v < 5.115.12.13 ≤ v < 5.135.13 ≤ v < 5.15.1005.13 ≤ v < 6.1.185.13 ≤ v < 6.2.55.13 ≤ v < 6.35.16 ≤ v < 6.1.185.4.128 ≤ v < 5.56.2 ≤ v < 6.2.53bef21035888dd19750ad79b5d08fe52a02ad7194.19.1965.10.465.12.135.135.4.1288d396bb0a5b62b326f6be7594d8bd46b088296bdafd8b0d091d5b4febe2d0ac3b7735c1826329302d7e403eea007f47776186d4d572f234b1221e6e3e52d43c82f2f6556f0b7a790c19c072c1e99a95f
Vendor states this is fixed in bab872b638130a18fd54d9adfad7db77ed6457be (fixed)
Vendor states this is fixed in be308d68785b205e483b3a0c61ba3a82da468f2c (fixed)
Vendor states this is fixed in ce234af49d103d95e3fdca59b25e0d0242f41bb4 (fixed)
Vendor states this is fixed in cf52c320cf74245ce1c12b0bd48f77b87d77fbc9 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.100 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.18 (unaffected)
Vendor states this is fixed in 6.2.5 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card