<?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 03:39:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64454 — usb: dwc3: run gadget disconnect from sleepable suspend context</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64454</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: run gadget disconnect from sleepable suspend context&lt;/p&gt;
&lt;p&gt;dwc3_gadget_suspend() takes dwc-&amp;gt;lock with IRQs disabled and then calls
dwc3_disconnect_gadget().  For async callbacks that helper only uses
plain spin_unlock()/spin_lock(), so the gadget -&amp;gt;disconnect() callback
still runs with IRQs disabled and any sleepable callback trips Lockdep.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the dwc3_gadget_suspend() -&amp;gt;
dwc3_disconnect_gadget() -&amp;gt; gadget_driver-&amp;gt;disconnect() chain, and
Lockdep reported:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  gadget_disconnect+0x21/0x39 [vuln_msv]
  dwc3_gadget_suspend.constprop.0+0x2b/0x42 [vuln_msv]&lt;/p&gt;
&lt;p&gt;Keep the disconnect callback selection in one common helper, but add a
sleepable suspend-side wrapper which snapshots the callback under
dwc-&amp;gt;lock and then runs it after spin_unlock_irqrestore().  The regular
event path still uses the existing spin_unlock()/spin_lock() window.&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: run gadget disconnect from sleepable suspend context&lt;/p&gt;
&lt;p&gt;dwc3_gadget_suspend() takes dwc-&amp;gt;lock with IRQs disabled and then calls
dwc3_disconnect_gadget().  For async callbacks that helper only uses
plain spin_unlock()/spin_lock(), so the gadget -&amp;gt;disconnect() callback
still runs with IRQs disabled and any sleepable callback trips Lockdep.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the dwc3_gadget_suspend() -&amp;gt;
dwc3_disconnect_gadget() -&amp;gt; gadget_driver-&amp;gt;disconnect() chain, and
Lockdep reported:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  gadget_disconnect+0x21/0x39 [vuln_msv]
  dwc3_gadget_suspend.constprop.0+0x2b/0x42 [vuln_msv]&lt;/p&gt;
&lt;p&gt;Keep the disconnect callback selection in one common helper, but add a
sleepable suspend-side wrapper which snapshots the callback under
dwc-&amp;gt;lock and then runs it after spin_unlock_irqrestore().  The regular
event path still uses the existing spin_unlock()/spin_lock() window.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64454</guid>
    </item>
  </channel>
</rss>
