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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a Patch
- https://git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185 Patch
- https://git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- References+1 references (now 4)NVD modified 2026-10-21 13:18
- First seenCVSS 7.8 · linuxNVD modified 2026-10-19 21:10
Affected (CPE criteria) 4
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*
References 4
- https://git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a Patch
- https://git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185 Patch
- https://git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6 Patch
- https://git.kernel.org/stable/c/dc797a4bbbcac6d19e6e2508e4df685755cd94a5