bnxt_en: Fix memory corruption when FW resources change during ifdown
CVE-2025-39810 · published 16 Sept 2025
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2025-39810?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: ec5d31e3c15d5233b491400133c67f78a320062c to < dc797a4bbbcac6d19e6e2508e4df685755cd94a5, ec5d31e3c15d5233b491400133c67f78a320062c to < d00e98977ef519280b075d783653e2c492fffbb6, ec5d31e3c15d5233b491400133c67f78a320062c to < 9ab6a9950f152e094395d2e3967f889857daa185, ec5d31e3c15d5233b491400133c67f78a320062c to < 2747328ba2714f1a7454208dbbc1dc0631990b4a
- Linux Linux: 5.4
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Fix memory corruption when FW resources change during ifdown
bnxt_set_dflt_rings() assumes that it is always called before any TC has
been created. So it doesn't take bp->num_tc into account and assumes
that it is always 0 or 1.
In the FW resource or capability change scenario, the FW will return
flags in bnxt_hwrm_if_change() that will cause the driver to
reinitialize and call bnxt_cancel_reservations(). This will lead to
bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp->num_tc
may be greater than 1. This will cause bp->tx_ring[] to be sized too
small and cause memory corruption in bnxt_alloc_cp_rings().
Fix it by properly scaling the TX rings by bp->num_tc in the code
paths mentioned above. Add 2 helper functions to determine
bp->tx_nr_rings and bp->tx_nr_rings_per_tc.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/dc797a4bbbcac6d19e6e2508e4df685755cd94a5
- git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6
- git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185
- git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON