<?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 06:54:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37813 — usb: xhci: Fix invalid pointer dereference in Etron workaround</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37813</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: xhci: Fix invalid pointer dereference in Etron workaround&lt;/p&gt;
&lt;p&gt;This check is performed before prepare_transfer() and prepare_ring(), so
enqueue can already point at the final link TRB of a segment. And indeed
it will, some 0.4% of times this code is called.&lt;/p&gt;
&lt;p&gt;Then enqueue + 1 is an invalid pointer. It will crash the kernel right
away or load some junk which may look like a link TRB and cause the real
link TRB to be replaced with a NOOP. This wouldn&amp;#39;t end well.&lt;/p&gt;
&lt;p&gt;Use a functionally equivalent test which doesn&amp;#39;t dereference the pointer
and always gives correct result.&lt;/p&gt;
&lt;p&gt;Something has crashed my machine twice in recent days while playing with
an Etron HC, and a control transfer stress test ran for confirmation has
just crashed it again. The same test passes with this patch applied.&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: xhci: Fix invalid pointer dereference in Etron workaround&lt;/p&gt;
&lt;p&gt;This check is performed before prepare_transfer() and prepare_ring(), so
enqueue can already point at the final link TRB of a segment. And indeed
it will, some 0.4% of times this code is called.&lt;/p&gt;
&lt;p&gt;Then enqueue + 1 is an invalid pointer. It will crash the kernel right
away or load some junk which may look like a link TRB and cause the real
link TRB to be replaced with a NOOP. This wouldn&amp;#39;t end well.&lt;/p&gt;
&lt;p&gt;Use a functionally equivalent test which doesn&amp;#39;t dereference the pointer
and always gives correct result.&lt;/p&gt;
&lt;p&gt;Something has crashed my machine twice in recent days while playing with
an Etron HC, and a control transfer stress test ran for confirmation has
just crashed it again. The same test passes with this patch applied.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37813</guid>
    </item>
  </channel>
</rss>
