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 products
linux: linux kernel
References5
- git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a Patch
- git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185 Patch
- git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6 Patch
- git.kernel.org/stable/c/c0082a8947cf1a543013346d10c1857f0c57db83
- git.kernel.org/stable/c/dc797a4bbbcac6d19e6e2508e4df685755cd94a5
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 10 · as of 8 November 2026
- CWE
- CWE-787
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.