| 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-53241: x86/xen: don't do PV iret hypercall through hypercall page |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| x86/xen: don't do PV iret hypercall through hypercall page |
| |
| Instead of jumping to the Xen hypercall page for doing the iret |
| hypercall, directly code the required sequence in xen-asm.S. |
| |
| This is done in preparation of no longer using hypercall page at all, |
| as it has shown to cause problems with speculation mitigations. |
| |
| This is part of XSA-466 / CVE-2024-53241. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53241 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.232 with commit 05df6e6cd9a76b778aee33c3c18c9f3b3566d4a5 |
| Fixed in 5.15.175 with commit c7b4cfa6213a44fa48714186dfdf125072d036e3 |
| Fixed in 6.1.121 with commit fa719857f613fed94a79da055b13ca51214c694f |
| Fixed in 6.6.67 with commit 82c211ead1ec440dbf81727e17b03b5e3c44b93d |
| Fixed in 6.12.6 with commit f7c3fdad0a474062d566aae3289d490d7e702d30 |
| Fixed in 6.13 with commit a2796dff62d6c6bfc5fbebdf2bee0d5ac0438906 |
| |
| 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-53241 |
| 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/xen/xen-asm.S |
| |
| |
| 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/05df6e6cd9a76b778aee33c3c18c9f3b3566d4a5 |
| https://git.kernel.org/stable/c/c7b4cfa6213a44fa48714186dfdf125072d036e3 |
| https://git.kernel.org/stable/c/fa719857f613fed94a79da055b13ca51214c694f |
| https://git.kernel.org/stable/c/82c211ead1ec440dbf81727e17b03b5e3c44b93d |
| https://git.kernel.org/stable/c/f7c3fdad0a474062d566aae3289d490d7e702d30 |
| https://git.kernel.org/stable/c/a2796dff62d6c6bfc5fbebdf2bee0d5ac0438906 |
