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 CONFIGUSBDWC3DUALROLE 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: dwc3suspendcommon() spinlockirqsave(&dwc->lock, flags); <-- 1st dwc3gadgetsuspend(dwc); dwc3gadgetsoftdisconnect(dwc); spinlockirqsave(&dwc->lock, flags); <-- 2nd This issue is exposed by commit c7ebd8149ee5 ("usb: dwc3: gadget: Fix NULL pointer dereference in dwc3gadgetsuspend") that removes the code of checking whether dwc->gadgetdriver 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-42085?
CVE-2024-42085 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-42085?
To fix CVE-2024-42085, upgrade the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.
Which versions of the Linux kernel are affected by CVE-2024-42085?
CVE-2024-42085 affects Linux kernel versions between 5.15.128 and 5.15.162, and multiple versions up to 6.6.37.
Is there a specific configuration that exposes CVE-2024-42085?
Yes, the vulnerability occurs when CONFIG_USB_DWC3_DUAL_ROLE is selected and a system enters suspend status.
What could be the potential impact of CVE-2024-42085?
The potential impact of CVE-2024-42085 could include deadlock scenarios during gadget suspend/resume operations.