[CVE-2026-72039][LOW] bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()

[CVE-2026-72039][LOW] bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()

[AL-KERNEL]

CVE: CVE-2026-72039
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()
Commit: 58594ed2a2f859ffb93edbbfa4aabb7739bea383
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=58594ed2a2f859ffb93edbbfa4aabb7739bea383
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72039
Analysis date: Sun, 16 Aug 2026 00:16:02 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A privileged bnx2x driver initialization failure can leak the fastpath allocation when a later tpa_info allocation fails, but the issue is not network reachable and has only limited DoS potential through repeated resource leakage.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72039 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72039

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72039	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'A memory leak in the bnx2x driver allocation path can occur when bnx2x_alloc_mem_bp allocates the fastpath array but a later fp tpa_info allocation fails before the array is linked into the bp structure. In that error path the normal cleanup code cannot find and free the earlier allocation, so repeated failed initialization attempts can leak kernel memory. For the CVSS the PR:H is selected because reliable triggering normally requires administrative control over the PCI network driver load, probe, reset, or fault injection environment. The issue is not network reachable and cannot be triggered by ordinary packet traffic. Impact is denial of service through limited resource leakage only, with no evidence of UAF, OOB access, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)	YES	REMOTE SIMPLEFIX LEAK ERRORPATH NETWORK LINUS  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Triggered signals:

* Availability impact realistic: +1 only in a weak theoretical sense. Repeated failed initialization could leak kernel memory over time.
* Requires admin/root/CAP or equivalent in typical deployments: -2. Reliable triggering normally requires driver probe, reload, reset, device management, or fault injection control.
* Rare and hardware-specific condition: -1. The path requires the bnx2x driver and Broadcom hardware or a comparable probe environment.
* Resource leak only. No UAF, double free, OOB access, stale pointer reuse, attacker-controlled reclaim, or write primitive is shown.

Effective score is floored at 0.

## 3. Reachability analysis

The bug is in `bnx2x_alloc_mem_bp()` during driver memory allocation. It is reached during driver or device initialization, not from normal packet RX/TX processing. An attacker would need to cause allocation of `fp` to succeed and later allocation of `fp[i].tpa_info` to fail before cleanup. In normal deployments this implies privileged device control, driver reload, probe manipulation, memory pressure under admin control, or fault injection.

Namespaces or containers do not materially lower the requirement unless a container is given meaningful host device management privileges. Ordinary local users cannot reliably trigger this path. The issue is not remotely network-triggerable and cannot be reached by sending packets to the NIC.

## 4. Severity interpretation

This behaves like a Low or ordinary Moderate resource-leak issue, not an actionable Moderate and not an Important-class kernel vulnerability. The bug is an error-path memory leak in a privileged driver initialization path. The realistic impact is limited availability degradation only if the failure path can be triggered repeatedly. There is no supported memory corruption primitive and no plausible privilege escalation path from the provided patch context.

## 5. One-sentence report phrase

A privileged bnx2x driver initialization failure can leak the fastpath allocation when a later tpa_info allocation fails, but the issue is not network reachable and has only limited DoS potential through repeated resource leakage.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This is a privileged, hardware-specific allocation error-path memory leak with no evidence of UAF, OOB access, attacker-controlled corruption, information disclosure, or privilege escalation.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()
Commit: 58594ed2a2f859ffb93edbbfa4aabb7739bea383
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=58594ed2a2f859ffb93edbbfa4aabb7739bea383

Commit description:

If the allocation of fp[i].tpa_info fails, the error path will not free
the struct bnx2x_fastpath allocated earlier, as it is not linked to the
bp structure yet. Fix that by linking it immediately after allocation.

Cc: stable@vger.kernel.org
Fixes: 15192a8 ("bnx2x: Split the FP structure")
Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/20260620062402.89549-1-nihaal@cse.iitm.ac.in
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=58594ed2a2f859ffb93edbbfa4aabb7739bea383

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72039 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72039

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.1

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 0

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).