<?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>Sun, 04 Oct 2026 15:32:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43324 — USB: dummy-hcd: Fix interrupt synchronization error</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43324</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: dummy-hcd: Fix interrupt synchronization error&lt;/p&gt;
&lt;p&gt;This fixes an error in synchronization in the dummy-hcd driver.  The
error has a somewhat involved history.  The synchronization mechanism
was introduced by commit 7dbd8f4cabd9 (&amp;#34;USB: dummy-hcd: Fix erroneous
synchronization change&amp;#34;), which added an emulated &amp;#34;interrupts enabled&amp;#34;
flag together with code emulating synchronize_irq() (it waits until
all current handler callbacks have returned).&lt;/p&gt;
&lt;p&gt;But the emulated interrupt-disable occurred too late, after the driver
containing the handler callback routines had been told that it was
unbound and no more callbacks would occur.  Commit 4a5d797a9f9c (&amp;#34;usb:
gadget: dummy_hcd: fix gpf in gadget_setup&amp;#34;) tried to fix this by
moving the synchronize_irq() emulation code from dummy_stop() to
dummy_pullup(), which runs before the unbind callback.&lt;/p&gt;
&lt;p&gt;There still were races, though, because the emulated interrupt-disable
still occurred too late.  It couldn&amp;#39;t be moved to dummy_pullup(),
because that routine can be called for reasons other than an impending
unbind.  Therefore commits 7dc0c55e9f30 (&amp;#34;USB: UDC core: Add
udc_async_callbacks gadget op&amp;#34;) and 04145a03db9d (&amp;#34;USB: UDC: Implement
udc_async_callbacks in dummy-hcd&amp;#34;) added an API allowing the UDC core
to tell dummy-hcd exactly when emulated interrupts and their callbacks
should be disabled.&lt;/p&gt;
&lt;p&gt;That brings us to the current state of things, which is still wrong
because the emul…&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: dummy-hcd: Fix interrupt synchronization error&lt;/p&gt;
&lt;p&gt;This fixes an error in synchronization in the dummy-hcd driver.  The
error has a somewhat involved history.  The synchronization mechanism
was introduced by commit 7dbd8f4cabd9 (&amp;#34;USB: dummy-hcd: Fix erroneous
synchronization change&amp;#34;), which added an emulated &amp;#34;interrupts enabled&amp;#34;
flag together with code emulating synchronize_irq() (it waits until
all current handler callbacks have returned).&lt;/p&gt;
&lt;p&gt;But the emulated interrupt-disable occurred too late, after the driver
containing the handler callback routines had been told that it was
unbound and no more callbacks would occur.  Commit 4a5d797a9f9c (&amp;#34;usb:
gadget: dummy_hcd: fix gpf in gadget_setup&amp;#34;) tried to fix this by
moving the synchronize_irq() emulation code from dummy_stop() to
dummy_pullup(), which runs before the unbind callback.&lt;/p&gt;
&lt;p&gt;There still were races, though, because the emulated interrupt-disable
still occurred too late.  It couldn&amp;#39;t be moved to dummy_pullup(),
because that routine can be called for reasons other than an impending
unbind.  Therefore commits 7dc0c55e9f30 (&amp;#34;USB: UDC core: Add
udc_async_callbacks gadget op&amp;#34;) and 04145a03db9d (&amp;#34;USB: UDC: Implement
udc_async_callbacks in dummy-hcd&amp;#34;) added an API allowing the UDC core
to tell dummy-hcd exactly when emulated interrupts and their callbacks
should be disabled.&lt;/p&gt;
&lt;p&gt;That brings us to the current state of things, which is still wrong
because the emul…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43324</guid>
    </item>
  </channel>
</rss>
