| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025091616-CVE-2025-39823-f9bf@gregkh> Date: Tue, 16 Sep 2025 15:00:29 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: KVM: x86: use array_index_nospec with indices that come from guest min and dest_id are guest-controlled indices. Using array_index_nospec() after the bounds checks clamps these values to mitigate speculative execution side-channels. The Linux kernel CVE team has assigned CVE-2025-39823 to this issue. Affected and fixed versions =========================== Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 5.4.298 with commit 72777fc31aa7ab2ce00f44bfa3929c6eabbeaf48 Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 5.10.242 with commit 31a0ad2f60cb4816e06218b63e695eb72ce74974 Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 5.15.191 with commit d51e381beed5e2f50f85f49f6c90e023754efa12 Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 6.1.150 with commit 33e974c2d5a82b2f9d9ba0ad9cbaabc1c8e3985f Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 6.6.104 with commit f49161646e03d107ce81a99c6ca5da682fe5fb69 Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 6.12.45 with commit 67a05679621b7f721bdba37a5d18665d3aceb695 Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 6.16.5 with commit f57a4bd8d6cb5af05b8ac1be9098e249034639fb Issue introduced in 4.19 with commit 4180bf1b655a791a0a6ef93a2ffffc762722c782 and fixed in 6.17-rc4 with commit c87bd4dd43a624109c3cc42d843138378a7f4548 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-39823 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/kvm/lapic.c arch/x86/kvm/x86.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/72777fc31aa7ab2ce00f44bfa3929c6eabbeaf48 https://git.kernel.org/stable/c/31a0ad2f60cb4816e06218b63e695eb72ce74974 https://git.kernel.org/stable/c/d51e381beed5e2f50f85f49f6c90e023754efa12 https://git.kernel.org/stable/c/33e974c2d5a82b2f9d9ba0ad9cbaabc1c8e3985f https://git.kernel.org/stable/c/f49161646e03d107ce81a99c6ca5da682fe5fb69 https://git.kernel.org/stable/c/67a05679621b7f721bdba37a5d18665d3aceb695 https://git.kernel.org/stable/c/f57a4bd8d6cb5af05b8ac1be9098e249034639fb https://git.kernel.org/stable/c/c87bd4dd43a624109c3cc42d843138378a7f4548
Powered by blists - more mailing lists