<?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 11:35:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89450 — iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89450</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;iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field&lt;/p&gt;
&lt;p&gt;tegra241_vintf_init_vsid() programs the guest-provided vSID into SID_MATCH,
whose VIRT_SID field spans bits [20:1] with bit 0 as the match-enable flag.
The HW therefore matches only a 20-bit Stream ID.&lt;/p&gt;
&lt;p&gt;The bound check rejects only virt_sid &amp;gt; UINT_MAX, which admits a value far
wider than the field. The write &amp;#34;virt_sid &amp;lt;&amp;lt; 1 | 0x1&amp;#34; then drops every bit
above 20: a virt_sid of 0x80000000 lands as SID_MATCH = 0x1, a valid match
on vSID 0, so the entry aliases the wrong Stream ID. Because vdev-&amp;gt;virt_id
is guest-controlled, a VMM can trigger it.&lt;/p&gt;
&lt;p&gt;Validate virt_sid against the field width with FIELD_MAX(), and program the
register with FIELD_PREP() so the value and the field stay consistent.&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;iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field&lt;/p&gt;
&lt;p&gt;tegra241_vintf_init_vsid() programs the guest-provided vSID into SID_MATCH,
whose VIRT_SID field spans bits [20:1] with bit 0 as the match-enable flag.
The HW therefore matches only a 20-bit Stream ID.&lt;/p&gt;
&lt;p&gt;The bound check rejects only virt_sid &amp;gt; UINT_MAX, which admits a value far
wider than the field. The write &amp;#34;virt_sid &amp;lt;&amp;lt; 1 | 0x1&amp;#34; then drops every bit
above 20: a virt_sid of 0x80000000 lands as SID_MATCH = 0x1, a valid match
on vSID 0, so the entry aliases the wrong Stream ID. Because vdev-&amp;gt;virt_id
is guest-controlled, a VMM can trigger it.&lt;/p&gt;
&lt;p&gt;Validate virt_sid against the field width with FIELD_MAX(), and program the
register with FIELD_PREP() so the value and the field stay consistent.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89450</guid>
    </item>
  </channel>
</rss>
