<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T15:48:11.833048+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64454</id>
    <title>CVE-2026-64454 — usb: dwc3: run gadget disconnect from sleepable suspend context</title>
    <updated>2026-09-30T15:48:11.849930+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>usb: dwc3: run gadget disconnect from sleepable suspend context</p>
<p>dwc3_gadget_suspend() takes dwc-&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 -&gt;disconnect() callback
still runs with IRQs disabled and any sleepable callback trips Lockdep.</p>
<p>This issue was found by our static analysis tool and then manually
reviewed against the current tree.</p>
<p>The grounded PoC kept the dwc3_gadget_suspend() -&gt;
dwc3_disconnect_gadget() -&gt; gadget_driver-&gt;disconnect() chain, and
Lockdep reported:</p>
<p>BUG: sleeping function called from invalid context
  gadget_disconnect+0x21/0x39 [vuln_msv]
  dwc3_gadget_suspend.constprop.0+0x2b/0x42 [vuln_msv]</p>
<p>Keep the disconnect callback selection in one common helper, but add a
sleepable suspend-side wrapper which snapshots the callback under
dwc-&gt;lock and then runs it after spin_unlock_irqrestore().  The regular
event path still uses the existing spin_unlock()/spin_lock() window.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64454"/>
  </entry>
</feed>
