# CVE-2025-40330: bnxt_en: Shutdown FW DMA in bnxt_shutdown()

> A flaw in the bnxt_en driver allows memory corruption during kexec, potentially leading to denial of service or code execution in the new kernel.

- **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:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40330, DEBIAN-CVE-2025-40330, GHSA-fj8r-2x4x-2q83, UBUNTU-CVE-2025-40330

## What is CVE-2025-40330?

CVE-2025-40330 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. 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:

bnxt_en: Shutdown FW DMA in bnxt_shutdown()

The netif_close() call in bnxt_shutdown() only stops packet DMA.  There
may be FW DMA for trace logging (recently added) that will continue.  If
we kexec to a new kernel, the DMA will corrupt memory in the new kernel.

Add bnxt_hwrm_func_drv_unrgtr() to unregister the driver from the FW.
This will stop the FW DMA.  In case the call fails, call pcie_flr() to
reset the function and stop the DMA.

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


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

Apply the vendor's patch.

## Is CVE-2025-40330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40330 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. 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-2025-40330 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-40330/ (Markdown: https://insights.sbomify.com/CVE-2025-40330/index.md)
```

## Sources

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

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