CVE-2025-39810

bnxt_en: Fix memory corruption when FW resources change during ifdown

HIGH
7.8
CVSS Score
Published: September 16, 2025 at 01:00 PM UTC
Updated: October 21, 2026 at 01:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 6.12.456.13 ≤ v < 6.16.55.46.176.17 rc16.17 rc26.17 rc3ec5d31e3c15d5233b491400133c67f78a320062c
Vendor states this is fixed in 2747328ba2714f1a7454208dbbc1dc0631990b4a (fixed)
Vendor states this is fixed in 9ab6a9950f152e094395d2e3967f889857daa185 (fixed)
Vendor states this is fixed in d00e98977ef519280b075d783653e2c492fffbb6 (fixed)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.12.45 (unaffected)
Vendor states this is fixed in 6.16.5 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)

References (4)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card