| 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-23155: net: stmmac: Fix accessing freed irq affinity_hint |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: stmmac: Fix accessing freed irq affinity_hint |
| |
| The cpumask should not be a local variable, since its pointer is saved |
| to irq_desc and may be accessed from procfs. |
| To fix it, use the persistent mask cpumask_of(cpu#). |
| |
| The Linux kernel CVE team has assigned CVE-2025-23155 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.13 with commit 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and fixed in 6.13.12 with commit e148266e104fce396ad624079a6812ac3a9982ef |
| Issue introduced in 5.13 with commit 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and fixed in 6.14.3 with commit 9e51a6a44e2c4de780a26e8fe110d708e806a8cd |
| Issue introduced in 5.13 with commit 8deec94c6040bb4a767f6e9456a0a44c7f2e713e and fixed in 6.15 with commit c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef |
| |
| 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-23155 |
| 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/stmicro/stmmac/stmmac_main.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/e148266e104fce396ad624079a6812ac3a9982ef |
| https://git.kernel.org/stable/c/9e51a6a44e2c4de780a26e8fe110d708e806a8cd |
| https://git.kernel.org/stable/c/c60d101a226f18e9a8f01bb4c6ca2b47dfcb15ef |
