# bnxt_en: Fix double invocation of bnxt_ulp_stop()/bnxt_ulp_start()

CVE record · `CVE-2025-38186`

- **Identifiers:** `CVE-2025-38186`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Jul 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Jul 2025, 13:37 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: `3c163f35bd50314d4e70ed9e83e1d8d83c473325 to before 6f2cd309492924b8afd2c62aebff815c1119d124` (git)
  - affected: `3c163f35bd50314d4e70ed9e83e1d8d83c473325 to before cca4ffd4a5b768752b91f6f75d77928e47886913` (git)
  - affected: `3c163f35bd50314d4e70ed9e83e1d8d83c473325 to before 1e9ac33fa271be0d2480fd732f9642d81542500b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.10`
  - unaffected: `before 6.10` (semver)
  - unaffected: `6.12.35 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.4 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 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.

> The Linux kernel bnxt_en driver (Broadcom NetXtreme-C/E Ethernet) is affected in versions from 6.10 before the fixed releases, with the fix backported to stable branches 6.12.35 and 6.15.4 and later. A bug let bnxt_ulp_stop() and bnxt_ulp_start() be invoked out of pairs after a new restart path was added, so the RoCE aux driver's suspend method could run twice and crash on a NULL pointer. The source does not describe an attacker-controlled trigger, and it gives no details on the impact beyond a kernel crash. Upgrade to a kernel release containing the fix; no workaround is described.

Written 16 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 4 Jul 2025, 13:37 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38186)
- 4 Jul 2025, 14:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38186)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/6f2cd309492924b8afd2c62aebff815c1119d124>
- <https://git.kernel.org/stable/c/cca4ffd4a5b768752b91f6f75d77928e47886913>
- <https://git.kernel.org/stable/c/1e9ac33fa271be0d2480fd732f9642d81542500b>

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-38186>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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