<?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>Fri, 02 Oct 2026 16:10:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-40927 — xhci: Handle TD clearing for multiple streams case</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-40927</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;xhci: Handle TD clearing for multiple streams case&lt;/p&gt;
&lt;p&gt;When multiple streams are in use, multiple TDs might be in flight when
an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for
each, to ensure everything is reset properly and the caches cleared.
Change the logic so that any N&amp;gt;1 TDs found active for different streams
are deferred until after the first one is processed, calling
xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to
queue another command until we are done with all of them. Also change
the error/&amp;#34;should never happen&amp;#34; paths to ensure we at least clear any
affected TDs, even if we can&amp;#39;t issue a command to clear the hardware
cache, and complain loudly with an xhci_warn() if this ever happens.&lt;/p&gt;
&lt;p&gt;This problem case dates back to commit e9df17eb1408 (&amp;#34;USB: xhci: Correct
assumptions about number of rings per endpoint.&amp;#34;) early on in the XHCI
driver&amp;#39;s life, when stream support was first added.
It was then identified but not fixed nor made into a warning in commit
674f8438c121 (&amp;#34;xhci: split handling halted endpoints into two steps&amp;#34;),
which added a FIXME comment for the problem case (without materially
changing the behavior as far as I can tell, though the new logic made
the problem more obvious).&lt;/p&gt;
&lt;p&gt;Then later, in commit 94f339147fc3 (&amp;#34;xhci: Fix failure to give back some
cached cancelled URBs.&amp;#34;), it was acknowledged again.&lt;/p&gt;
&lt;p&gt;[Mathias: commit 94f339147fc3 (&amp;#34;xhci: Fix failure to…&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;xhci: Handle TD clearing for multiple streams case&lt;/p&gt;
&lt;p&gt;When multiple streams are in use, multiple TDs might be in flight when
an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for
each, to ensure everything is reset properly and the caches cleared.
Change the logic so that any N&amp;gt;1 TDs found active for different streams
are deferred until after the first one is processed, calling
xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to
queue another command until we are done with all of them. Also change
the error/&amp;#34;should never happen&amp;#34; paths to ensure we at least clear any
affected TDs, even if we can&amp;#39;t issue a command to clear the hardware
cache, and complain loudly with an xhci_warn() if this ever happens.&lt;/p&gt;
&lt;p&gt;This problem case dates back to commit e9df17eb1408 (&amp;#34;USB: xhci: Correct
assumptions about number of rings per endpoint.&amp;#34;) early on in the XHCI
driver&amp;#39;s life, when stream support was first added.
It was then identified but not fixed nor made into a warning in commit
674f8438c121 (&amp;#34;xhci: split handling halted endpoints into two steps&amp;#34;),
which added a FIXME comment for the problem case (without materially
changing the behavior as far as I can tell, though the new logic made
the problem more obvious).&lt;/p&gt;
&lt;p&gt;Then later, in commit 94f339147fc3 (&amp;#34;xhci: Fix failure to give back some
cached cancelled URBs.&amp;#34;), it was acknowledged again.&lt;/p&gt;
&lt;p&gt;[Mathias: commit 94f339147fc3 (&amp;#34;xhci: Fix failure to…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-40927</guid>
    </item>
  </channel>
</rss>
