CVE-2023-53054
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2023-53054
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53054.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2023-53054
- Related
- Published
- 2025-05-02T16:15:24Z
- Modified
- 2025-05-05T22:50:05.236931Z
- Summary
- [none]
- Details
-
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: _dwc2lowlevelhwenable -> devmaddactionorreset(). This adds a new devres each time. This may also happen at runtime, as dwc2lowlevelhwenable() can be called from udcstart().
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: ... devreslog: 49000000.usb-otg ADD 82a13bba devmactionrelease (8 bytes) ... devreslog: 49000000.usb-otg ADD 49889daf devmactionrelease (8 bytes) ...
A second issue is addressed here: - regulatorbulkenable() is called upon each PM cycle (suspend/resume). - regulatorbulkdisable() never gets called.
So the reference count for these regulators constantly increase, by one upon each low power cycle, due to missing regulatorbulkdisable() call in _dwc2lowlevelhwdisable().
The original fix that introduced the devmaddactionorreset() call, fixed an issue during probe, that happens due to other errors in dwc2driverprobe() -> dwc2corereset(). Then the probe fails without disabling regulators, when drmode == USBDRMODEPERIPHERAL.
Rather fix the error path: disable all the low level hardware in the error path, by using the "hsotg->llhwenabled" flag. Checking drmode has been introduced to avoid a dual call to dwc2lowlevelhwdisable(). "llhwenabled" should achieve the same (and is used currently in the remove() routine).
- References
-
- https://git.kernel.org/stable/c/1f01027c51eb16145e8e07fafea3ca07ef102d06
- https://git.kernel.org/stable/c/6485fc381b6528b6f547ee1ff10bdbcbe31a6e4c
- https://git.kernel.org/stable/c/cba76e1fb896b573f09f51aa299223276a77bc90
- https://git.kernel.org/stable/c/f747313249b74f323ddf841a9c8db14d989f296a
- https://git.kernel.org/stable/c/ffb8ab6f87bd28d700ab5c20d9d3a7e75067630d
- https://security-tracker.debian.org/tracker/CVE-2023-53054
Affected packages
Debian:11 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0Unknown introduced version / All previous versions are affectedFixed5.10.178-1
Affected versions
5.*
Debian:12 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source