Bug 2541215 (CVE-2026-97572) - CVE-2026-97572 kernel: bnxt_en: Propagate RX ring init failures in bnxt_init_nic()
Summary: CVE-2026-97572 kernel: bnxt_en: Propagate RX ring init failures in bnxt_init_...
Keywords:
Status: NEW
Alias: CVE-2026-97572
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 11:03 UTC by OSIDB Bzimport
Modified: 2026-09-29 04:47 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 11:03:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.