CVE-2023-53415
published 2025-09-18CVE-2023-53415: In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.14%
3.4th percentile
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
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.19.196 < 4.20 | 4.20 |
| linux | linux | >= 5.10.46 < 5.11 | 5.11 |
| linux | linux | >= 5.12.13 < 5.13 | 5.13 |
| linux | linux | >= 5.4.128 < 5.5 | 5.5 |
| linux | linux | >= 8d396bb0a5b62b326f6be7594d8bd46b088296bd < cf52c320cf74245ce1c12b0bd48f77b87d77fbc9 | cf52c320cf74245ce1c12b0bd48f77b87d77fbc9 |
| linux | linux | >= 8d396bb0a5b62b326f6be7594d8bd46b088296bd < ce234af49d103d95e3fdca59b25e0d0242f41bb4 | ce234af49d103d95e3fdca59b25e0d0242f41bb4 |
| linux | linux | >= 8d396bb0a5b62b326f6be7594d8bd46b088296bd < bab872b638130a18fd54d9adfad7db77ed6457be | bab872b638130a18fd54d9adfad7db77ed6457be |
| linux | linux | >= 8d396bb0a5b62b326f6be7594d8bd46b088296bd < be308d68785b205e483b3a0c61ba3a82da468f2c | be308d68785b205e483b3a0c61ba3a82da468f2c |
| linux | linux_kernel | < 5.15.100 | 5.15.100 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 5.16 < 6.1.18 | 6.1.18 |
| linux | linux_kernel | >= 6.2 < 6.2.5 | 6.2.5 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: USB: dwc3: fix memory leak with using debugfs_lookup()
vendor_redhat·2025-09-18·CVSS 5.5
CVE-2023-53415 [MEDIUM] CWE-772 kernel: USB: dwc3: fix memory leak with using debugfs_lookup()
kernel: 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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Debian
CVE-2023-53415: linux - In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: ...
vendor_debian·2023·CVSS 5.5
CVE-2023-53415 [MEDIUM] CVE-2023-53415: linux - In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: ...
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.
Scope: local
bookworm: resolved (fixed in 6.1.20-1)
bullseye: open
forky: resolved (fixed in 6.1.20-1)
sid: resolved (fixed in 6.1.20-1)
trixie: resolved (fixed in 6.1.20-1)
OSV
CVE-2023-53415: In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: fix memory leak with using debugfs_lookup() When calling debugfs_lookup
osv·2025-09-18·CVSS 5.5
CVE-2023-53415 [MEDIUM] CVE-2023-53415: In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: fix memory leak with using debugfs_lookup() When calling 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.
GHSA
GHSA-gw7v-q6j5-h9mv: In the Linux kernel, the following vulnerability has been resolved:
USB: dwc3: fix memory leak with using debugfs_lookup()
When calling debugfs_look
ghsa_unreviewed·2025-09-18
CVE-2023-53415 [MEDIUM] CWE-401 GHSA-gw7v-q6j5-h9mv: In the Linux kernel, the following vulnerability has been resolved:
USB: dwc3: fix memory leak with using debugfs_lookup()
When calling debugfs_look
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.
No detection rules found.
No public exploits indexed.
2025-09-18
Published