CVE-2024-42085: usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock
When config CONFIG_USB_DWC3_DUAL_ROLE is selected, and trigger system
to enter suspend status with below command:
echo mem > /sys/power/state
There will be a deadlock issue occurring. Detailed invoking path as
below:
dwc3_suspend_common()
spin_lock_irqsave(&dwc->lock, flags); <-- 1st
dwc3_gadget_suspend(dwc);
dwc3_gadget_soft_disconnect(dwc);
spin_lock_irqsave(&dwc->lock, flags); <-- 2nd
This issue is exposed by commit c7ebd8149ee5 ("usb: dwc3: gadget: Fix
NULL pointer dereference in dwc3_gadget_suspend") that removes the code
of checking whether dwc->gadget_driver is NULL or not. It causes the
following code is executed and deadlock occurs when trying to get the
spinlock. In fact, the root cause is the commit 5265397f9442("usb: dwc3:
Remove DWC3 locking during gadget suspend/resume") that forgot to remove
the lock of otg mode. So, remove the redundant lock of otg mode during
gadget suspend/resume.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel USB controller bug that can deadlock a system during suspend on devices using DWC3 dual-role USB mode. For affected servers, appliances, phones, or embedded devices, the business impact is mainly availability: the device may hang during power-state changes until updated.
Executive priority
Treat this as a targeted availability issue. It should be scheduled with normal kernel maintenance, but prioritize field devices, appliances, and embedded platforms where a suspend-time hang would require manual recovery or disrupt service.
Technical view
In Linux USB DWC3 core, CONFIG_USB_DWC3_DUAL_ROLE can deadlock during system suspend because dwc3_suspend_common takes dwc->lock and dwc3_gadget_soft_disconnect later tries to take the same spinlock. Stable fixes remove redundant OTG-mode locking during gadget suspend/resume. The source bundle does not include CVSS, CWE, or detailed privilege prerequisites.
Likely exposure
Exposure is likely limited to Linux systems with DWC3 USB dual-role support enabled and reachable suspend/resume paths. General-purpose Linux hosts without this controller or configuration are less likely to be affected. Embedded, mobile, appliance, and USB OTG-capable platforms deserve closer review.
Exploitation context
The provided sources do not show active exploitation, public weaponization, or CISA KEV listing. The described trigger is system suspend with the vulnerable DWC3 dual-role path, suggesting availability risk rather than data theft or direct remote compromise based on available evidence.
Researcher notes
The evidence ties the flaw to a locking regression in the DWC3 gadget suspend/resume path. The bundle identifies fixed stable commits and Debian LTS coverage, but does not provide CVSS, exploitability analysis, or proof of real-world attacks.
Mitigation direction
Upgrade to a vendor kernel containing the referenced Linux stable fixes.
For Debian LTS systems, review and apply the referenced Debian security update.
Prioritize devices using DWC3 dual-role USB and suspend/resume workflows.
Check vendor advisories before applying non-distribution kernel changes.
If unpatched, reduce reliance on vulnerable suspend workflows where operationally acceptable.
Validation and detection
Inventory Linux systems with DWC3 USB dual-role support enabled.
Compare running kernel versions against vendor advisories and listed stable fix commits.
Review kernel package changelogs for CVE-2024-42085 or the DWC3 locking fix.
Test suspend/resume stability in a controlled environment after patching.
Confirm Debian LTS package status where Debian kernels are used.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-42085 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.