# bnxt_en: Fix memory corruption when FW resources change during ifdown

CVE record · `CVE-2025-39810`

- **Identifiers:** `CVE-2025-39810`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 16 Sept 2025
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 16 Sept 2025, 13:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ec5d31e3c15d5233b491400133c67f78a320062c to before c0082a8947cf1a543013346d10c1857f0c57db83` (git)
  - affected: `ec5d31e3c15d5233b491400133c67f78a320062c to before dc797a4bbbcac6d19e6e2508e4df685755cd94a5` (git)
  - affected: `ec5d31e3c15d5233b491400133c67f78a320062c to before d00e98977ef519280b075d783653e2c492fffbb6` (git)
  - affected: `ec5d31e3c15d5233b491400133c67f78a320062c to before 9ab6a9950f152e094395d2e3967f889857daa185` (git)
  - affected: `ec5d31e3c15d5233b491400133c67f78a320062c to before 2747328ba2714f1a7454208dbbc1dc0631990b4a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.4`
  - unaffected: `before 5.4` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.45 to 6.12.*, inclusive` (semver)
  - unaffected: `6.16.5 to 6.16.*, inclusive` (semver)
  - unaffected: `6.17 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions from 5.4 up to (but not including) the fixed releases are affected by a memory corruption bug in the bnxt_en Broadcom network driver. The flaw occurs when firmware resources change during an interface shutdown, causing transmit rings to be sized too small when traffic classes are configured. Fixes are available in the stable kernel releases listed in the advisory, so upgrade to a fixed kernel version for your branch.

Written 13 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 16 Sept 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-39810](https://www.cve.org/CVERecord?id=CVE-2025-39810)
- [NVD: CVE-2025-39810](https://nvd.nist.gov/vuln/detail/CVE-2025-39810)

### References from the CNA

- <https://git.kernel.org/stable/c/c0082a8947cf1a543013346d10c1857f0c57db83>
- <https://git.kernel.org/stable/c/dc797a4bbbcac6d19e6e2508e4df685755cd94a5>
- <https://git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6>
- <https://git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185>
- <https://git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-39810>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-39810/>. Everything for agents: <https://agentprime.io/llms.txt>.
