bnx2x: fix double free in bnx2x_init_firmware() error path (CVE-2026-89582) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89582

bnx2x: fix double free in bnx2x_init_firmware() error path

Answer in brief

CVE-2026-89582 records a Unknown severity vulnerability in bnx2x: fix double free in bnx2x_init_firmware() error path. 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 11, 2026Updated Sep 11, 2026Source checked Sep 11, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 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	>=94a78b79cb5f14c09a42522738d6694c6a1cdd20 <dc98e727b9cfc5e19c796bf893878153f00b222b \|\| >=94a78b79cb5f14c09a42522738d6694c6a1cdd20 <4d36e38e48340a1ccf92a98c7a22d07a954e5aa3 \|\| >=94a78b79cb5f14c09a42522738d6694c6a1cdd20 <a142c024f07d623e2b6b25943f6c36d4b6b0b4c6 \|\| >=94a78b79cb5f14c09a42522738d6694c6a1cdd20 <d2796ffe38cb4155afe0eab23636295b096c27a5	dc98e727b9cfc5e19c796bf893878153f00b222b, 4d36e38e48340a1ccf92a98c7a22d07a954e5aa3, a142c024f07d623e2b6b25943f6c36d4b6b0b4c6, d2796ffe38cb4155afe0eab23636295b096c27a5
Linux/Linuxgeneric	2.6.31	Not reported

Recommended response

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

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: bnx2x: fix double free in bnx2x_init_firmware() error path bnx2x_init_firmware() frees bp->init_ops, bp->init_data and bp->init_ops_offsets in its error path without setting them to NULL. The cleanup function bnx2x_release_firmware() frees the same three pointers unconditionally, so if init_firmware fails and release_firmware is later called (e.g. from __bnx2x_remove or through the function state machine), all three are freed a second time. Set each pointer to NULL after kfree() in the error path so that the subsequent kfree(NULL) in bnx2x_release_firmware() is a safe no-op.

Quoted source text, attributed separately from HOL analysis.