# CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC

> A NULL pointer dereference in the be2net driver can cause a system crash when sending packets to the BMC.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2025
- **Updated:** 2 Jun 2026
- **Also known as:** AZL-71404, BELL-CVE-2025-40264, DEBIAN-CVE-2025-40264, GHSA-gvxj-xj5w-j8qf, ROOT-OS-DEBIAN-11-CVE-2025-40264, ROOT-OS-DEBIAN-12-CVE-2025-40264, ROOT-OS-DEBIAN-13-CVE-2025-40264, ROOT-OS-UBUNTU-2204-CVE-2025-40264, ROOT-OS-UBUNTU-2404-CVE-2025-40264, UBUNTU-CVE-2025-40264

## What is CVE-2025-40264?

CVE-2025-40264 is a vulnerability in Linux, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

be2net: pass wrb_params in case of OS2BMC

be_insert_vlan_in_pkt() is called with the wrb_params argument being NULL
at be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL
pointer when processing a workaround for specific packet, as commit
bc0c3405abbb ("be2net: fix a Tx stall bug caused by a specific ipv6
packet") states.

The correct way would be to pass the wrb_params from be_xmit().

## Which versions are affected by CVE-2025-40264?


## How do I fix CVE-2025-40264?

Apply the vendor's patch.

## Is CVE-2025-40264 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40264 and fix it if it is affected.

What it is: CVE-2025-40264 is a vulnerability in Linux, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40264 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-2025-40264/ (Markdown: https://insights.sbomify.com/CVE-2025-40264/index.md)
```

## Sources

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

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