<?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>Mon, 28 Sep 2026 23:47:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97570 — bnxt_en: Bound SW TPA IDs to prevent crashes</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97570</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: Bound SW TPA IDs to prevent crashes&lt;/p&gt;
&lt;p&gt;FW supports up to 1024 concurrent TPAs, so the FW TPA ID is in the range
0..1023 (see commit ec4d8e7cf024 (&amp;#34;bnxt_en: Add TPA ID mapping logic for
57500 chips.&amp;#34;)). bnxt_alloc_agg_idx is intended to wrap the FW ID down to a
software ID which is used to index rxr-&amp;gt;rx_tpa, and to generate a mapping
between FW IDs and the wrapped software ID.&lt;/p&gt;
&lt;p&gt;On a 57608 with firmware version 233, the firmware advertises 32
concurrent TPAs. As of the commit under fixes, bp-&amp;gt;max_tpa on this NIC
is set to 32.&lt;/p&gt;
&lt;p&gt;If the software ID from bnxt_alloc_agg_idx is above 31, this results in
an invalid address being loaded on this line:&lt;/p&gt;
&lt;p&gt;tpa_info = &amp;amp;rxr-&amp;gt;rx_tpa[agg_id];&lt;/p&gt;
&lt;p&gt;because rx_tpa is allocated with only bp-&amp;gt;max_tpa (32) entries. Writes
to tpa_info later in the code are out of bounds.&lt;/p&gt;
&lt;p&gt;This bug results in a crash at boot:&lt;/p&gt;
&lt;p&gt;Oops: general protection fault, kernel NULL pointer dereference 0x8: 0000 [#1] SMP NOPTI
RIP: 0010:bnxt_rx_pkt+0xc0/0x1560
RSP: 0018:ffffc900009b8c78 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000048 RCX: 0000000206682516
RDX: ffffc900009b8db4 RSI: 0000000000000000 RDI: 01ffffff038fe1c0
RBP: ffffc9006e687480 R08: ffffc9006e687000 R09: 0000000000003048
R10: 0000000000000480 R11: ffff8881c6083900 R12: 0000000006682516
R13: ffff8881c6095400 R14: 0000000000000016 R15: ffff8881c6b66680
FS:  0000000000000000(0000) GS:ffff88fef3c77000(0000) knlGS:0000000000000000
CS:…&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: Bound SW TPA IDs to prevent crashes&lt;/p&gt;
&lt;p&gt;FW supports up to 1024 concurrent TPAs, so the FW TPA ID is in the range
0..1023 (see commit ec4d8e7cf024 (&amp;#34;bnxt_en: Add TPA ID mapping logic for
57500 chips.&amp;#34;)). bnxt_alloc_agg_idx is intended to wrap the FW ID down to a
software ID which is used to index rxr-&amp;gt;rx_tpa, and to generate a mapping
between FW IDs and the wrapped software ID.&lt;/p&gt;
&lt;p&gt;On a 57608 with firmware version 233, the firmware advertises 32
concurrent TPAs. As of the commit under fixes, bp-&amp;gt;max_tpa on this NIC
is set to 32.&lt;/p&gt;
&lt;p&gt;If the software ID from bnxt_alloc_agg_idx is above 31, this results in
an invalid address being loaded on this line:&lt;/p&gt;
&lt;p&gt;tpa_info = &amp;amp;rxr-&amp;gt;rx_tpa[agg_id];&lt;/p&gt;
&lt;p&gt;because rx_tpa is allocated with only bp-&amp;gt;max_tpa (32) entries. Writes
to tpa_info later in the code are out of bounds.&lt;/p&gt;
&lt;p&gt;This bug results in a crash at boot:&lt;/p&gt;
&lt;p&gt;Oops: general protection fault, kernel NULL pointer dereference 0x8: 0000 [#1] SMP NOPTI
RIP: 0010:bnxt_rx_pkt+0xc0/0x1560
RSP: 0018:ffffc900009b8c78 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000048 RCX: 0000000206682516
RDX: ffffc900009b8db4 RSI: 0000000000000000 RDI: 01ffffff038fe1c0
RBP: ffffc9006e687480 R08: ffffc9006e687000 R09: 0000000000003048
R10: 0000000000000480 R11: ffff8881c6083900 R12: 0000000006682516
R13: ffff8881c6095400 R14: 0000000000000016 R15: ffff8881c6b66680
FS:  0000000000000000(0000) GS:ffff88fef3c77000(0000) knlGS:0000000000000000
CS:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97570</guid>
    </item>
  </channel>
</rss>
