CVE-2026-97572 json
bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
published 2026-09-25 44 d ago modified 2026-10-19 20 d ago also EUVD-2026-86880
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
bnxt_init_rx_rings() returns an error when bnxt_alloc_one_rx_ring() fails, but bnxt_init_nic() discards that return value and calls bnxt_init_chip(), which enables TPA.
If an allocation fails, this could leave rxr->rx_tpa[] partially zeroed and TPA would be enabled over an array with zeroed entries. This would lead to a zeroed DMA address being handed out if the agg_idx is translated to a SW index at a zeroed entry.
Fix this by propagating the error out of bnxt_init_nic(). Both callers already check its return value and unwind with bnxt_free_skbs() and bnxt_free_mem(), which tolerate a partially initialized RX ring.
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.7-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-97572
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-97572
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.39.1
- kernel-rt Linux Micro 6.2 6.12.0-160000.39.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.39.1
- kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.39.1
- kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.39.1.160000.2.26
- kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.39.1
- kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.39.1
- kernel-obs-qa SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.39.1
suse advisories SUSE-SU-2026:24197-1SUSE-SU-2026:24184-1SUSE-SU-2026:24235-1SUSE-SU-2026:24179-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.39.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.39.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.39.1
opensuse advisories openSUSE-SU-2026:22091-1openSUSE-SU-2026:12074-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-104741
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/e40641638743b4b848d5ed78a0565afffc359d8e commit
- git.kernel.org/stable/c/6b24eca42619b93f69aebc2aa0a9fd28ac9a5085 commit
- git.kernel.org/stable/c/1f2d333ae2e1a73b7cc1c2a627587024cd147c01 commit
- git.kernel.org/stable/c/c3eb07e78e628243cbb9bbb0115db802fb7a303f commit
- git.kernel.org/stable/c/daadccd062fdca5e77a8cc22ffe35857803b6c49 commit
- git.kernel.org/stable/c/b4c40f2c80d7bf50648878bc206a39adfbfaec6c commit
- git.kernel.org/stable/c/dfd73af81cdb9f7b399754a59e2658a08211bee5 commit
- git.kernel.org/stable/c/8e6a850c0746bb4be167aedf1ee57469fcda09a9 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97572 updated cvss 5.5
kernel: bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e40641638743b4b848d5ed78a0565afffc359d8e
- git.kernel.org /stable/c/6b24eca42619b93f69aebc2aa0a9fd28ac9a5085
- git.kernel.org /stable/c/1f2d333ae2e1a73b7cc1c2a627587024cd147c01
- git.kernel.org /stable/c/c3eb07e78e628243cbb9bbb0115db802fb7a303f
- git.kernel.org /stable/c/daadccd062fdca5e77a8cc22ffe35857803b6c49
- git.kernel.org /stable/c/b4c40f2c80d7bf50648878bc206a39adfbfaec6c
- git.kernel.org /stable/c/dfd73af81cdb9f7b399754a59e2658a08211bee5
- git.kernel.org /stable/c/8e6a850c0746bb4be167aedf1ee57469fcda09a9
Sources
- CVE List CVE-2026-97572
- NVD CVE-2026-97572
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.