Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53054: usb: dwc2: fix a devres leak in hw_enable upon suspend resume

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1f01027c51eb16145e8e07fafea3ca07ef102d06, 4.10, 4.15.

Low priority for now. Upgrade to Linux Linux 1f01027c51eb16145e8e07fafea3ca07ef102d06, 4.10, 4.15 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

Published
May 2, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53054

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • c95e1f67b9a84479d1a6d2e9b123a1553af2a75e, 7d2a4749e1589295c69183f7d79d5b62664b34d6, 8a8841b9f3eb1f46e3fc6d56a9b9299c53f4f86f, fa7fd9ba18533e9aa5f718a06de3deb522a4b587, b2c2b88b049684b89776036f9a03fcc2d1bb3c22, e7c4b79d70a70b4b7b0a04c640238a2ef0a7a8c8, 88dcd13872b11bd60e6d4cb6317821e1d367e524, 5.9affected
    • 33a06f1300a79cfd461cea0268f05e969d4f34ec and later · before 1f01027c51eb16145e8e07fafea3ca07ef102d06affected · git
    • 33a06f1300a79cfd461cea0268f05e969d4f34ec and later · before cba76e1fb896b573f09f51aa299223276a77bc90affected · git
    • 33a06f1300a79cfd461cea0268f05e969d4f34ec and later · before ffb8ab6f87bd28d700ab5c20d9d3a7e75067630daffected · git
    • 33a06f1300a79cfd461cea0268f05e969d4f34ec and later · before 6485fc381b6528b6f547ee1ff10bdbcbe31a6e4caffected · git
    • 33a06f1300a79cfd461cea0268f05e969d4f34ec and later · before f747313249b74f323ddf841a9c8db14d989f296aaffected · git
    • 4.4.233 and later · before 4.5affected · semver
    • 4.9.233 and later · before 4.10affected · semver
    • 4.14.194 and later · before 4.15affected · semver
    • 4.19.140 and later · before 4.20affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.25-16.1.25-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53047May 2, 2025 · tee: amdtee: fix race condition in amdtee_open_session
    18Monitor
  • ← EarlierCVE-2023-53052May 2, 2025 · cifs: fix use-after-free bug in refresh_cache_worker()
    31Monitor
  • Later →CVE-2023-53057May 2, 2025 · Bluetooth: HCI: Fix global-out-of-bounds
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1f01027c51eb16145e8e07fafea3ca07ef102d06Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux5.8Vendor (CNA)
Linux Linux5.9Vendor (CNA)
Linux Linux6485fc381b6528b6f547ee1ff10bdbcbe31a6e4cVendor (CNA)
Linux Linuxcba76e1fb896b573f09f51aa299223276a77bc90Vendor (CNA)
Linux Linuxf747313249b74f323ddf841a9c8db14d989f296aVendor (CNA)
Linux Linuxffb8ab6f87bd28d700ab5c20d9d3a7e75067630dVendor (CNA)
debian:linux6.1.25-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records