<?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-29T00:46:46.171118+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-2026-97574</id>
    <title>CVE-2026-97574 — bnxt_en: Don't free the live ring's TPA state on queue restart failure</title>
    <updated>2026-09-29T00:46:46.172721+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: Don't free the live ring's TPA state on queue restart failure</p>
<p>bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:</p>
<p>memcpy(clone, rxr, sizeof(*rxr));</p>
<p>the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.</p>
<p>If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring's memory can be freed while still in use.</p>
<p>Fix this by initializing the clone's pointers to NULL to prevent live
ring state from being freed inadvertently.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-97574"/>
  </entry>
</feed>
