Skip to main content
VulnerabilityPublished Updated

CVE-2026-72039: Linux kernel · bnx2x: fix potential memory leak in bnx2x_alloc_mem_bp()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c51b280b9cd3c9e97bf2cde33bb795c511f09669 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c51b280b9cd3c9e97bf2cde33bb795c511f09669, a986fde914d88af47eb78fd29c5d1af7952c3500, 356077547b1afa34a8ebae77176a577631a89041 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < c51b280b9cd3c9e97bf2cde33bb795c511f09669
Fixed in
  • c51b280b9cd3c9e97bf2cde33bb795c511f09669
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < a986fde914d88af47eb78fd29c5d1af7952c3500
Fixed in
  • a986fde914d88af47eb78fd29c5d1af7952c3500
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < 356077547b1afa34a8ebae77176a577631a89041
Fixed in
  • 356077547b1afa34a8ebae77176a577631a89041
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < 58594ed2a2f859ffb93edbbfa4aabb7739bea383
Fixed in
  • 58594ed2a2f859ffb93edbbfa4aabb7739bea383
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < 5576ee19a6a4aa111c61ce974e70bb79e7bb3952
Fixed in
  • 5576ee19a6a4aa111c61ce974e70bb79e7bb3952
LinuxLinuxAffected
  • ≥ 15192a8cf8a8d16e0ff38a144c8a4630c94f9fd6, < 7d8d454b5d24dbad346cd57ef315e7bf1ee8e856
Fixed in
  • 7d8d454b5d24dbad346cd57ef315e7bf1ee8e856

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.

References

Community reviews

Loading reviews…