bnxt_en: Don't free the live ring's TPA state on queue restart failure (CVE-2026-97574) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97574

bnxt_en: Don't free the live ring's TPA state on queue restart failure

Answer in brief

CVE-2026-97574 records a Unknown severity vulnerability in bnxt_en: Don't free the live ring's TPA state on queue restart failure. 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 <8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27 \|\| >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <0596a7caa6fc283e142716739099c038d8714082 \|\| >=bd649c5cc958169b8a8a3e77ea926d92d472b02a <5ce7f36c334d723954855ac769ede2fe0e8f89c8 \|\| 0997443906b96a051011f220a61e6dce4602ec54 \|\| >=6.12.20 <6.13	8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27, 0596a7caa6fc283e142716739099c038d8714082, 5ce7f36c334d723954855ac769ede2fe0e8f89c8, 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 8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27 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: Don't free the live ring's TPA state on queue restart failure bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone: memcpy(clone, rxr, sizeof(*rxr)); the code currently clears pointers that the clone owns (such as rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory of the live ring that was cloned. If an allocation failure happens later and the err_free_tpa_info label is taken, the live ring's memory can be freed while still in use. Fix this by initializing the clone's pointers to NULL to prevent live ring state from being freed inadvertently.

Quoted source text, attributed separately from HOL analysis.