| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37895: bnxt_en: Fix error handling path in bnxt_init_chip() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bnxt_en: Fix error handling path in bnxt_init_chip() |
| |
| WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails |
| because we call cancel_work_sync() on dim work that has not been |
| initialized. |
| |
| WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230 |
| |
| The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim |
| work has already been cancelled. But in the bnxt_open() path, |
| BNXT_STATE_NAPI_DISABLED is not set and this causes the error |
| path to think that it needs to cancel the uninitalized dim work. |
| Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization. |
| The bit will be cleared when we enable NAPI and initialize dim work. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37895 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.12.10 with commit f697217f980ffc796c72c34dbf7d59a6b1996888 and fixed in 6.12.28 with commit e039b00ddbfeaa0dc59b8659be114f1a1b37c5bf |
| Issue introduced in 6.13 with commit 40452969a50652e3cbf89dac83d54eebf2206d27 and fixed in 6.14.6 with commit 21116727f452474502ee74f956d5e7466103e19b |
| Issue introduced in 6.13 with commit 40452969a50652e3cbf89dac83d54eebf2206d27 and fixed in 6.15 with commit 9ab7a709c926c16b4433cf02d04fcbcf35aaab2b |
| |
| 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-37895 |
| 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/e039b00ddbfeaa0dc59b8659be114f1a1b37c5bf |
| https://git.kernel.org/stable/c/21116727f452474502ee74f956d5e7466103e19b |
| https://git.kernel.org/stable/c/9ab7a709c926c16b4433cf02d04fcbcf35aaab2b |
