| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56721: x86/CPU/AMD: Terminate the erratum_1386_microcode array |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| x86/CPU/AMD: Terminate the erratum_1386_microcode array |
| |
| The erratum_1386_microcode array requires an empty entry at the end. |
| Otherwise x86_match_cpu_with_stepping() will continue iterate the array after |
| it ended. |
| |
| Add an empty entry to erratum_1386_microcode to its end. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56721 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit 29ba89f1895285f06c333546882e0c5ae9a6df23 and fixed in 6.11.11 with commit 82d6b82cf89d950982ac240ba068c3a7e1f23b0a |
| Issue introduced in 6.10 with commit 29ba89f1895285f06c333546882e0c5ae9a6df23 and fixed in 6.12.2 with commit ccfee14f08b8699132b87bc6d78e0fa75bf094dd |
| Issue introduced in 6.10 with commit 29ba89f1895285f06c333546882e0c5ae9a6df23 and fixed in 6.13 with commit ff6cdc407f4179748f4673c39b0921503199a0ad |
| |
| 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-2024-56721 |
| 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/82d6b82cf89d950982ac240ba068c3a7e1f23b0a |
| https://git.kernel.org/stable/c/ccfee14f08b8699132b87bc6d78e0fa75bf094dd |
| https://git.kernel.org/stable/c/ff6cdc407f4179748f4673c39b0921503199a0ad |