<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 17:14:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42085 — usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-42085</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock&lt;/p&gt;
&lt;p&gt;When config CONFIG_USB_DWC3_DUAL_ROLE is selected, and trigger system
to enter suspend status with below command:
echo mem &amp;gt; /sys/power/state
There will be a deadlock issue occurring. Detailed invoking path as
below:
dwc3_suspend_common()
    spin_lock_irqsave(&amp;amp;dwc-&amp;gt;lock, flags);              &amp;lt;-- 1st
    dwc3_gadget_suspend(dwc);
        dwc3_gadget_soft_disconnect(dwc);
            spin_lock_irqsave(&amp;amp;dwc-&amp;gt;lock, flags);      &amp;lt;-- 2nd
This issue is exposed by commit c7ebd8149ee5 (&amp;#34;usb: dwc3: gadget: Fix
NULL pointer dereference in dwc3_gadget_suspend&amp;#34;) that removes the code
of checking whether dwc-&amp;gt;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(&amp;#34;usb: dwc3:
Remove DWC3 locking during gadget suspend/resume&amp;#34;) that forgot to remove
the lock of otg mode. So, remove the redundant lock of otg mode during
gadget suspend/resume.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: dwc3: core: remove lock of otg mode during gadget suspend/resume to avoid deadlock&lt;/p&gt;
&lt;p&gt;When config CONFIG_USB_DWC3_DUAL_ROLE is selected, and trigger system
to enter suspend status with below command:
echo mem &amp;gt; /sys/power/state
There will be a deadlock issue occurring. Detailed invoking path as
below:
dwc3_suspend_common()
    spin_lock_irqsave(&amp;amp;dwc-&amp;gt;lock, flags);              &amp;lt;-- 1st
    dwc3_gadget_suspend(dwc);
        dwc3_gadget_soft_disconnect(dwc);
            spin_lock_irqsave(&amp;amp;dwc-&amp;gt;lock, flags);      &amp;lt;-- 2nd
This issue is exposed by commit c7ebd8149ee5 (&amp;#34;usb: dwc3: gadget: Fix
NULL pointer dereference in dwc3_gadget_suspend&amp;#34;) that removes the code
of checking whether dwc-&amp;gt;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(&amp;#34;usb: dwc3:
Remove DWC3 locking during gadget suspend/resume&amp;#34;) that forgot to remove
the lock of otg mode. So, remove the redundant lock of otg mode during
gadget suspend/resume.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-42085</guid>
    </item>
  </channel>
</rss>
