linux-cve-announce - CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091614-CVE-2025-39810-ed5c@gregkh>
Date: Tue, 16 Sep 2025 15:00:16 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2025-39810 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 5.4 with commit ec5d31e3c15d5233b491400133c67f78a320062c and fixed in 6.12.45 with commit d00e98977ef519280b075d783653e2c492fffbb6
	Issue introduced in 5.4 with commit ec5d31e3c15d5233b491400133c67f78a320062c and fixed in 6.16.5 with commit 9ab6a9950f152e094395d2e3967f889857daa185
	Issue introduced in 5.4 with commit ec5d31e3c15d5233b491400133c67f78a320062c and fixed in 6.17-rc4 with commit 2747328ba2714f1a7454208dbbc1dc0631990b4a

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-39810
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/net/ethernet/broadcom/bnxt/bnxt.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/d00e98977ef519280b075d783653e2c492fffbb6
	https://git.kernel.org/stable/c/9ab6a9950f152e094395d2e3967f889857daa185
	https://git.kernel.org/stable/c/2747328ba2714f1a7454208dbbc1dc0631990b4a