CVE-2023-53054 json
usb: dwc2: fix a devres leak in hw_enable upon suspend resume
published last yr. modified 5mo ago also EUVD-2025-13212
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc2: fix a devres leak in hw_enable upon suspend resume
Each time the platform goes to low power, PM suspend / resume routines call: __dwc2_lowlevel_hw_enable -> devm_add_action_or_reset(). This adds a new devres each time. This may also happen at runtime, as dwc2_lowlevel_hw_enable() can be called from udc_start().
This can be seen with tracing: - echo 1 > /sys/kernel/debug/tracing/events/dev/devres_log/enable - go to low power - cat /sys/kernel/debug/tracing/trace
A new "ADD" entry is found upon each low power cycle: ... devres_log: 49000000.usb-otg ADD 82a13bba devm_action_release (8 bytes) ... devres_log: 49000000.usb-otg ADD 49889daf devm_action_release (8 bytes) ...
A second issue is addressed here: - regulator_bulk_enable() is called upon each PM cycle (suspend/resume). - regulator_bulk_disable() never gets called.
So the reference count for these regulators constantly increase, by one upon each low power cycle, due to missing regulator_bulk_disable() call in __dwc2_lowlevel_hw_disable().
The original fix that introduced the devm_add_action_or_reset() call, fixed an issue during probe, that happens due to other errors in dwc2_driver_probe() -> dwc2_core_reset(). Then the probe fails without disabling regulators, when dr_mode == USB_DR_MODE_PERIPHERAL.
Rather fix the error path: disable all the low level hardware in the error path, by using the "hsotg->ll_hw_enabled" flag. Checking dr_mode has been introduced to avoid a dual call to dwc2_lowlevel_hw_disable(). "ll_hw_enabled" should achieve the same (and is used currently in the remove() routine).
Patch / fix
- Linux Linux 4.5, 4.10, 4.15, 4.20, 5.5, 5.8, 5.9, 5.10.177, 5.15.105, 6.1.22, 6.2.9, 6.3
- linux Debian 14, Debian 13, Debian 12 6.1.25-1
debian advisories DEBIAN-CVE-2023-53054
- linux Ubuntu 22.04 LTS 5.15.0-79.86
- linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
- linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1035.38
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-azure Ubuntu 22.04 LTS 5.15.0-1045.52
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1025.30
ubuntu advisories UBUNTU-CVE-2023-53054
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.167.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.167.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.167.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +7 more 5.14.21-150400.24.167.1
- kernel-zfcpdump SLES 15 SP4-LTSS, Manager Server 4.3 5.14.21-150400.24.167.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.167.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.167.1.150400.24.84.1
- kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.110.1
suse advisories SUSE-SU-2025:02262-1SUSE-SU-2025:02173-1SUSE-SU-2025:01966-1SUSE-SU-2025:01918-1
- git.kernel.org/stable/c/1f01027c51eb16145e8e07fafea3ca07ef102d06 commit
- git.kernel.org/stable/c/cba76e1fb896b573f09f51aa299223276a77bc90 commit
- git.kernel.org/stable/c/ffb8ab6f87bd28d700ab5c20d9d3a7e75067630d commit
- git.kernel.org/stable/c/6485fc381b6528b6f547ee1ff10bdbcbe31a6e4c commit
- git.kernel.org/stable/c/f747313249b74f323ddf841a9c8db14d989f296a commit
Is CVE-2023-53054 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53054 updated cvss 5.5
kernel: usb: dwc2: fix a devres leak in hw_enable upon suspend resume
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/1f01027c51eb16145e8e07fafea3ca07ef102d06
patch
-
git.kernel.org
/stable/c/cba76e1fb896b573f09f51aa299223276a77bc90
patch
-
git.kernel.org
/stable/c/ffb8ab6f87bd28d700ab5c20d9d3a7e75067630d
patch
-
git.kernel.org
/stable/c/6485fc381b6528b6f547ee1ff10bdbcbe31a6e4c
patch
-
git.kernel.org
/stable/c/f747313249b74f323ddf841a9c8db14d989f296a
patch
Sources
- CVE List CVE-2023-53054
- NVD CVE-2023-53054
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.