CVE-2026-97571

bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()

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 TPA buffer allocation failures in bnxt_queue_mem_alloc() bnxt_alloc_one_tpa_info_data() returns -ENOMEM as soon as one allocation fails. This leaves the remaining rxr->rx_tpa[] entries zeroed. bnxt_queue_mem_alloc() discards that return value, so the partially initialized ring is installed by bnxt_queue_start(). Since the agg_id is picked by the hardware and bnxt_alloc_agg_idx maps it to a SW index in rxr->rx_tpa[], it is possible that an uninitialized slot can be chosen which would hand a zero DMA address to the device. Fix this by checking the return value of bnxt_alloc_one_tpa_info_data and unwinding, freeing the ring buffers.

Affected

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

0997443906b96a051011f220a61e6dce4602ec546.12.206.13997443906b96a51011f220a61e6dce4602ec54bd649c5cc958169b8a8a3e77ea926d92d472b02a
Vendor states this is fixed in 37e08dc821a57fe0592c917486b638caa888b46d (fixed)
Vendor states this is fixed in b814dfbfeb0a68c9a52073f2caa05a2d5247a329 (fixed)
Vendor states this is fixed in c8050386a2209b2a474c1eb4bd1574dc19129bfb (fixed)
Vendor states this is fixed in d7db2e4953e4626339fd0075564a3e447650d37b (fixed)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.53 (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