# CVE-2026-72039: bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()

> A memory leak in the bnx2x network driver can lead to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72039, DEBIAN-CVE-2026-72039, GHSA-gq9w-rcq5-q8jh, UBUNTU-CVE-2026-72039

## What is CVE-2026-72039?

CVE-2026-72039 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()

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.

## Which versions are affected by CVE-2026-72039?


## How do I fix CVE-2026-72039?

Apply the vendor's patch.

## Is CVE-2026-72039 being exploited?

There is no known exploitation of CVE-2026-72039 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72039 and fix it if it is affected.

What it is: CVE-2026-72039 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72039 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72039/ (Markdown: https://insights.sbomify.com/CVE-2026-72039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72039
- OSV: https://osv.dev/vulnerability/CVE-2026-72039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72039/
Summaries are generated and may contain mistakes; the official description above is the record.