<?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>Tue, 29 Sep 2026 14:28:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68370 — usb: gadget: dummy_hcd: prevent fifo_req reuse during giveback</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68370</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: gadget: dummy_hcd: prevent fifo_req reuse during giveback&lt;/p&gt;
&lt;p&gt;dummy_hcd embeds a single shared usb_request (dum-&amp;gt;fifo_req) that the
&amp;#34;emulated single-request FIFO&amp;#34; fast-path in dummy_queue() reuses for
small IN transfers: it copies the caller&amp;#39;s request into it
(req-&amp;gt;req = *_req) and queues it, treating list_empty(&amp;amp;fifo_req.queue)
as &amp;#34;the slot is free&amp;#34;.&lt;/p&gt;
&lt;p&gt;The completion side (dummy_timer/transfer/nuke/dummy_dequeue) follows
the standard pattern: list_del_init(&amp;amp;req-&amp;gt;queue) unlinks the request,
then the lock is dropped and usb_gadget_giveback_request() invokes
req-&amp;gt;complete().  But list_del_init() makes fifo_req.queue look empty
*before* the completion callback returns, so a concurrent dummy_queue()
on another CPU sees the slot as free, reuses fifo_req and runs
req-&amp;gt;req = *_req -- overwriting req-&amp;gt;complete while dummy_timer is
mid-calling it.  The indirect call then jumps to a clobbered pointer,
causing a general protection fault / page fault in dummy_timer
(syzkaller extid faf3a6cf579fc65591ca).  The clobbering write is an
in-bounds memcpy on a live shared object, so KASAN cannot flag it.&lt;/p&gt;
&lt;p&gt;Add a fifo_req_busy bit covering the shared request&amp;#39;s whole lifetime:
set it in dummy_queue() when the FIFO fast-path takes fifo_req (making
it the fast-path guard, replacing the list_empty(&amp;amp;fifo_req.queue)
test), and clear it after the completion callback has returned, via a
dummy_giveback() helper used at all four gadget-…&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: gadget: dummy_hcd: prevent fifo_req reuse during giveback&lt;/p&gt;
&lt;p&gt;dummy_hcd embeds a single shared usb_request (dum-&amp;gt;fifo_req) that the
&amp;#34;emulated single-request FIFO&amp;#34; fast-path in dummy_queue() reuses for
small IN transfers: it copies the caller&amp;#39;s request into it
(req-&amp;gt;req = *_req) and queues it, treating list_empty(&amp;amp;fifo_req.queue)
as &amp;#34;the slot is free&amp;#34;.&lt;/p&gt;
&lt;p&gt;The completion side (dummy_timer/transfer/nuke/dummy_dequeue) follows
the standard pattern: list_del_init(&amp;amp;req-&amp;gt;queue) unlinks the request,
then the lock is dropped and usb_gadget_giveback_request() invokes
req-&amp;gt;complete().  But list_del_init() makes fifo_req.queue look empty
*before* the completion callback returns, so a concurrent dummy_queue()
on another CPU sees the slot as free, reuses fifo_req and runs
req-&amp;gt;req = *_req -- overwriting req-&amp;gt;complete while dummy_timer is
mid-calling it.  The indirect call then jumps to a clobbered pointer,
causing a general protection fault / page fault in dummy_timer
(syzkaller extid faf3a6cf579fc65591ca).  The clobbering write is an
in-bounds memcpy on a live shared object, so KASAN cannot flag it.&lt;/p&gt;
&lt;p&gt;Add a fifo_req_busy bit covering the shared request&amp;#39;s whole lifetime:
set it in dummy_queue() when the FIFO fast-path takes fifo_req (making
it the fast-path guard, replacing the list_empty(&amp;amp;fifo_req.queue)
test), and clear it after the completion callback has returned, via a
dummy_giveback() helper used at all four gadget-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68370</guid>
    </item>
  </channel>
</rss>
