CVE-2026-97572

bnxt_en: Propagate RX ring init failures in bnxt_init_nic()

N/A
Published: September 25, 2026 at 10:21 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4c0c050c58d840994ba842ad1c338a98e7c12b764
Vendor states this is fixed in 1f2d333ae2e1a73b7cc1c2a627587024cd147c01 (fixed)
Vendor states this is fixed in 6b24eca42619b93f69aebc2aa0a9fd28ac9a5085 (fixed)
Vendor states this is fixed in 8e6a850c0746bb4be167aedf1ee57469fcda09a9 (fixed)
Vendor states this is fixed in b4c40f2c80d7bf50648878bc206a39adfbfaec6c (fixed)
Vendor states this is fixed in c3eb07e78e628243cbb9bbb0115db802fb7a303f (fixed)
Vendor states this is fixed in daadccd062fdca5e77a8cc22ffe35857803b6c49 (fixed)
Vendor states this is fixed in dfd73af81cdb9f7b399754a59e2658a08211bee5 (fixed)
Vendor states this is fixed in e40641638743b4b848d5ed78a0565afffc359d8e (fixed)
Vendor states this is fixed in 4.4 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card