| 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-37873: eth: bnxt: fix missing ring index trim on error path |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| eth: bnxt: fix missing ring index trim on error path |
| |
| Commit under Fixes converted tx_prod to be free running but missed |
| masking it on the Tx error path. This crashes on error conditions, |
| for example when DMA mapping fails. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37873 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.8 with commit 6d1add95536bafe585c500ad8114af7ed4225a0f and fixed in 6.12.25 with commit 21e70f694bc0dcb40174b0940cc52a7769fc19e0 |
| Issue introduced in 6.8 with commit 6d1add95536bafe585c500ad8114af7ed4225a0f and fixed in 6.14.4 with commit 3742c55de00266fa7c8fd2c5d61a453d223a9cd1 |
| Issue introduced in 6.8 with commit 6d1add95536bafe585c500ad8114af7ed4225a0f and fixed in 6.15 with commit 12f2d033fae957d84c2c0ce604d2a077e61fa2c0 |
| |
| 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-37873 |
| 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/21e70f694bc0dcb40174b0940cc52a7769fc19e0 |
| https://git.kernel.org/stable/c/3742c55de00266fa7c8fd2c5d61a453d223a9cd1 |
| https://git.kernel.org/stable/c/12f2d033fae957d84c2c0ce604d2a077e61fa2c0 |
