<?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 03:39:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39810 — bnxt_en: Fix memory corruption when FW resources change during ifdown</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39810</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;bnxt_en: Fix memory corruption when FW resources change during ifdown&lt;/p&gt;
&lt;p&gt;bnxt_set_dflt_rings() assumes that it is always called before any TC has
been created.  So it doesn&amp;#39;t take bp-&amp;gt;num_tc into account and assumes
that it is always 0 or 1.&lt;/p&gt;
&lt;p&gt;In the FW resource or capability change scenario, the FW will return
flags in bnxt_hwrm_if_change() that will cause the driver to
reinitialize and call bnxt_cancel_reservations().  This will lead to
bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp-&amp;gt;num_tc
may be greater than 1.  This will cause bp-&amp;gt;tx_ring[] to be sized too
small and cause memory corruption in bnxt_alloc_cp_rings().&lt;/p&gt;
&lt;p&gt;Fix it by properly scaling the TX rings by bp-&amp;gt;num_tc in the code
paths mentioned above.  Add 2 helper functions to determine
bp-&amp;gt;tx_nr_rings and bp-&amp;gt;tx_nr_rings_per_tc.&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;bnxt_en: Fix memory corruption when FW resources change during ifdown&lt;/p&gt;
&lt;p&gt;bnxt_set_dflt_rings() assumes that it is always called before any TC has
been created.  So it doesn&amp;#39;t take bp-&amp;gt;num_tc into account and assumes
that it is always 0 or 1.&lt;/p&gt;
&lt;p&gt;In the FW resource or capability change scenario, the FW will return
flags in bnxt_hwrm_if_change() that will cause the driver to
reinitialize and call bnxt_cancel_reservations().  This will lead to
bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp-&amp;gt;num_tc
may be greater than 1.  This will cause bp-&amp;gt;tx_ring[] to be sized too
small and cause memory corruption in bnxt_alloc_cp_rings().&lt;/p&gt;
&lt;p&gt;Fix it by properly scaling the TX rings by bp-&amp;gt;num_tc in the code
paths mentioned above.  Add 2 helper functions to determine
bp-&amp;gt;tx_nr_rings and bp-&amp;gt;tx_nr_rings_per_tc.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39810</guid>
    </item>
  </channel>
</rss>
