<?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 12:11:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74585 — thunderbolt: Bound the DROM dual link port number before indexing sw-&gt;ports</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74585</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;thunderbolt: Bound the DROM dual link port number before indexing sw-&amp;gt;ports&lt;/p&gt;
&lt;p&gt;tb_drom_parse_entry_port() validates the device-supplied header-&amp;gt;index
against sw-&amp;gt;config.max_port_number before indexing sw-&amp;gt;ports[], but the
sibling field entry-&amp;gt;dual_link_port_nr -- a 6-bit value also read from
the DROM -- indexes the same array with no such check. A malicious or
malformed Thunderbolt device can set dual_link_port_nr beyond the
allocated sw-&amp;gt;ports[] (max_port_number + 1 entries), producing an
out-of-bounds tb_port pointer that is stored and later dereferenced.&lt;/p&gt;
&lt;p&gt;Reject a port entry whose dual_link_port_nr exceeds max_port_number,
the same bound already applied to header-&amp;gt;index.&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;thunderbolt: Bound the DROM dual link port number before indexing sw-&amp;gt;ports&lt;/p&gt;
&lt;p&gt;tb_drom_parse_entry_port() validates the device-supplied header-&amp;gt;index
against sw-&amp;gt;config.max_port_number before indexing sw-&amp;gt;ports[], but the
sibling field entry-&amp;gt;dual_link_port_nr -- a 6-bit value also read from
the DROM -- indexes the same array with no such check. A malicious or
malformed Thunderbolt device can set dual_link_port_nr beyond the
allocated sw-&amp;gt;ports[] (max_port_number + 1 entries), producing an
out-of-bounds tb_port pointer that is stored and later dereferenced.&lt;/p&gt;
&lt;p&gt;Reject a port entry whose dual_link_port_nr exceeds max_port_number,
the same bound already applied to header-&amp;gt;index.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74585</guid>
    </item>
  </channel>
</rss>
