Vulnerability intelligence
CVE-2025-39810 and is rated High severity with a CVSS score of 7.8. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.
This update corrects flaws in the following subsystems: - HID subsystem; - InfiniBand drivers; - Network drivers; - PCI subsystem; - SCSI subsystem; - JFS file system; - Network file system (NFS) client; - OCFS2 file system; (CVE-2022-49082, CVE-2025-39730, CVE-2025-39743, CVE-2025-39783, CVE-2025-39810, CVE-2025-39824, CVE-2026-74350, CVE-2026-74394)
This update corrects flaws in the following subsystems: - HID subsystem; - InfiniBand drivers; - Network drivers; - PCI subsystem; - JFS file system; - OCFS2 file system; (CVE-2025-39743, CVE-2025-39783, CVE-2025-39810, CVE-2025-39824, CVE-2026-74350, CVE-2026-74394)
Release Notes
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.
Source: NVD