<?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 09:43:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43205 — dpaa2-switch: validate num_ifs to prevent out-of-bounds write</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43205</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;dpaa2-switch: validate num_ifs to prevent out-of-bounds write&lt;/p&gt;
&lt;p&gt;The driver obtains sw_attr.num_ifs from firmware via dpsw_get_attributes()
but never validates it against DPSW_MAX_IF (64). This value controls
iteration in dpaa2_switch_fdb_get_flood_cfg(), which writes port indices
into the fixed-size cfg-&amp;gt;if_id[DPSW_MAX_IF] array. When firmware reports
num_ifs &amp;gt;= 64, the loop can write past the array bounds.&lt;/p&gt;
&lt;p&gt;Add a bound check for num_ifs in dpaa2_switch_init().&lt;/p&gt;
&lt;p&gt;dpaa2_switch_fdb_get_flood_cfg() appends the control interface (port
num_ifs) after all matched ports. When num_ifs == DPSW_MAX_IF and all
ports match the flood filter, the loop fills all 64 slots and the control
interface write overflows by one entry.&lt;/p&gt;
&lt;p&gt;The check uses &amp;gt;= because num_ifs == DPSW_MAX_IF is also functionally
broken.&lt;/p&gt;
&lt;p&gt;build_if_id_bitmap() silently drops any ID &amp;gt;= 64:
      if (id[i] &amp;lt; DPSW_MAX_IF)
          bmap[id[i] / 64] |= ...&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;dpaa2-switch: validate num_ifs to prevent out-of-bounds write&lt;/p&gt;
&lt;p&gt;The driver obtains sw_attr.num_ifs from firmware via dpsw_get_attributes()
but never validates it against DPSW_MAX_IF (64). This value controls
iteration in dpaa2_switch_fdb_get_flood_cfg(), which writes port indices
into the fixed-size cfg-&amp;gt;if_id[DPSW_MAX_IF] array. When firmware reports
num_ifs &amp;gt;= 64, the loop can write past the array bounds.&lt;/p&gt;
&lt;p&gt;Add a bound check for num_ifs in dpaa2_switch_init().&lt;/p&gt;
&lt;p&gt;dpaa2_switch_fdb_get_flood_cfg() appends the control interface (port
num_ifs) after all matched ports. When num_ifs == DPSW_MAX_IF and all
ports match the flood filter, the loop fills all 64 slots and the control
interface write overflows by one entry.&lt;/p&gt;
&lt;p&gt;The check uses &amp;gt;= because num_ifs == DPSW_MAX_IF is also functionally
broken.&lt;/p&gt;
&lt;p&gt;build_if_id_bitmap() silently drops any ID &amp;gt;= 64:
      if (id[i] &amp;lt; DPSW_MAX_IF)
          bmap[id[i] / 64] |= ...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43205</guid>
    </item>
  </channel>
</rss>
