CVE-2026-97573

bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset()

HIGH
8.1
CVSS Score
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
HIGH8.1
Exploit prediction
EPSS 0.6%

Description

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() bnxt_rx_ring_reset() frees the ring buffers and then reallocates them, ignoring the result. bnxt_alloc_one_rx_ring() can fail in bnxt_alloc_one_tpa_info_data(), which returns -ENOMEM on the first failed allocation and leaves the remaining rxr->rx_tpa[] entries zeroed. The error isn't propagated up, so the loop in bnxt_rx_ring_reset continues and at the end the code re-enables TPA with partially unallocated rx_tpa array. This means that when the agg_id from hardware is mapped to a SW index in rxr->rx_tpa[], an uninitialized slot can be chosen which would hand a zero DMA address to the device. Fix this by falling back to a global reset, which is what the existing code already does when other functions fail, but unlike the other failure cases this particular failure has to return because TPA can't be re-enabled since the allocation failed.

Affected

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

5.108fbf58e17dce8f250dda9ad6b0a49b3041f0af14
Vendor states this is fixed in 1a3670b6a6b5679fe56c5890157b344f091e64f8 (fixed)
Vendor states this is fixed in 40b4a7bb6b0b872b45f017dbf211268de098b75c (fixed)
Vendor states this is fixed in 4a17c73c83798c2fa9c7920ad5a98803adce3e01 (fixed)
Vendor states this is fixed in 52fc97cbc3ba118aad84e7c001bf02ebe8496f70 (fixed)
Vendor states this is fixed in 8b2fd5c0aeda935294159206af9d6179282d425a (fixed)
Vendor states this is fixed in 961e2a17c5e3559b3f8654d2daabdd25a42e770a (fixed)
Vendor states this is fixed in af9a2bdaba0b4ceb0fc5e5122ef3fc6b7e5a366a (fixed)
Vendor states this is fixed in cfec9e7f15a56cb0104bac13d01e5d11e1ba84fb (fixed)
Vendor states this is fixed in 5.10 (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.

CVSS

8.1HIGHLinux
Vector?

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