<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T18:04:49.570193+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-39810</id>
    <title>CVE-2025-39810 — bnxt_en: Fix memory corruption when FW resources change during ifdown</title>
    <updated>2026-09-29T18:04:49.962463+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bnxt_en: Fix memory corruption when FW resources change during ifdown</p>
<p>bnxt_set_dflt_rings() assumes that it is always called before any TC has
been created.  So it doesn't take bp-&gt;num_tc into account and assumes
that it is always 0 or 1.</p>
<p>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-&gt;num_tc
may be greater than 1.  This will cause bp-&gt;tx_ring[] to be sized too
small and cause memory corruption in bnxt_alloc_cp_rings().</p>
<p>Fix it by properly scaling the TX rings by bp-&gt;num_tc in the code
paths mentioned above.  Add 2 helper functions to determine
bp-&gt;tx_nr_rings and bp-&gt;tx_nr_rings_per_tc.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-39810"/>
  </entry>
</feed>
