bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc() (CVE-2026-97571) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97571

bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc()

Answer in brief

CVE-2026-97571 records a Unknown severity vulnerability in bnxt_en: Propagate TPA buffer allocation failures in bnxt_queue_mem_alloc(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=bd649c5cc958169b8a8a3e77ea926d92d472b02a <c8050386a2209b2a474c1eb4bd1574dc19129bfb \|\| >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <37e08dc821a57fe0592c917486b638caa888b46d \|\| >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <b814dfbfeb0a68c9a52073f2caa05a2d5247a329 \|\| 0997443906b96a051011f220a61e6dce4602ec54 \|\| >=6.12.20 <6.13	c8050386a2209b2a474c1eb4bd1574dc19129bfb, 37e08dc821a57fe0592c917486b638caa888b46d, b814dfbfeb0a68c9a52073f2caa05a2d5247a329, 6.13
Linux/Linuxgeneric	6.13	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to c8050386a2209b2a474c1eb4bd1574dc19129bfb if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.