| 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-37751: x86/cpu: Avoid running off the end of an AMD erratum table |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| x86/cpu: Avoid running off the end of an AMD erratum table |
| |
| The NULL array terminator at the end of erratum_1386_microcode was |
| removed during the switch from x86_cpu_desc to x86_cpu_id. This |
| causes readers to run off the end of the array. |
| |
| Replace the NULL. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37751 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.14 with commit f3f3251526739bb975b97f840c56b3054dba8638 and fixed in 6.14.3 with commit 1b518f73f1b6f59e083ec33dea22d9a1a275a970 |
| Issue introduced in 6.14 with commit f3f3251526739bb975b97f840c56b3054dba8638 and fixed in 6.15 with commit f0df00ebc57f803603f2a2e0df197e51f06fbe90 |
| |
| 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-37751 |
| 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: |
| arch/x86/kernel/cpu/amd.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/1b518f73f1b6f59e083ec33dea22d9a1a275a970 |
| https://git.kernel.org/stable/c/f0df00ebc57f803603f2a2e0df197e51f06fbe90 |
