CVE-2023-53054 Details
Description
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).
A vulnerability in the Linux kernel's USB DWC2 driver has been addressed, concerning a development resource (devres) leak and improper management of regulator reference counts during power management cycles. The issue arises because the hardware enable function, called during suspend and resume operations, adds a new devres action each time, leading to a cumulative leak. This devres_log tracing reveals an 'ADD' entry for each low power cycle, indicating the leak. Additionally, the regulator bulk enable function is called with each power management cycle, but the corresponding disable function is never invoked, causing the reference count for these regulators to increase continuously. The vulnerability could also manifest at runtime, further complicating the resource management.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version where this issue has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1f01027c51eb16145e8e07fafea3ca07ef102d06 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6485fc381b6528b6f547ee1ff10bdbcbe31a6e4c | kernel.org | Patch |
| https://git.kernel.org/stable/c/cba76e1fb896b573f09f51aa299223276a77bc90 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f747313249b74f323ddf841a9c8db14d989f296a | kernel.org | Patch |
| https://git.kernel.org/stable/c/ffb8ab6f87bd28d700ab5c20d9d3a7e75067630d | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-401 | Missing Release of Memory after Effective Lifetime | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.4.233, < 4.5 >= 4.9.233, < 4.10 >= 4.14.194, < 4.15 >= 4.19.140, < 4.20 >= 5.4.59, < 5.5 >= 5.7.16, < 5.8 >= 5.8.2, < 5.10.177 >= 5.11, < 5.15.105 >= 5.16, < 6.1.22 >= 6.2, < 6.2.9 6.3 rc1 6.3 rc2 6.3 rc3 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 12, 2025 | Initial Analysis | [email protected] |
| May 2, 2025 | New CVE Received | kernel.org |