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: <2025050918-CVE-2025-37849-2a30@gregkh> Date: Fri, 9 May 2025 08:42:27 +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-37849: KVM: arm64: Tear down vGIC on failed vCPU creation From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Tear down vGIC on failed vCPU creation If kvm_arch_vcpu_create() fails to share the vCPU page with the hypervisor, we propagate the error back to the ioctl but leave the vGIC vCPU data initialised. Note only does this leak the corresponding memory when the vCPU is destroyed but it can also lead to use-after-free if the redistributor device handling tries to walk into the vCPU. Add the missing cleanup to kvm_arch_vcpu_create(), ensuring that the vGIC vCPU structures are destroyed on error. The Linux kernel CVE team has assigned CVE-2025-37849 to this issue. Affected and fixed versions =========================== Fixed in 6.1.135 with commit 07476e0d932afc53c05468076393ac35d0b4999e Fixed in 6.6.88 with commit 5085e02362b9948f82fceca979b8f8e12acb1cc5 Fixed in 6.12.24 with commit c322789613407647a05ff5c451a7bf545fb34e73 Fixed in 6.13.12 with commit 2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52 Fixed in 6.14.3 with commit f1e9087abaeedec9bf2894a282ee4f0d8383f299 Fixed in 6.15-rc1 with commit 250f25367b58d8c65a1b060a2dda037eea09a672 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-37849 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/arm64/kvm/arm.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/07476e0d932afc53c05468076393ac35d0b4999e https://git.kernel.org/stable/c/5085e02362b9948f82fceca979b8f8e12acb1cc5 https://git.kernel.org/stable/c/c322789613407647a05ff5c451a7bf545fb34e73 https://git.kernel.org/stable/c/2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52 https://git.kernel.org/stable/c/f1e9087abaeedec9bf2894a282ee4f0d8383f299 https://git.kernel.org/stable/c/250f25367b58d8c65a1b060a2dda037eea09a672
Powered by blists - more mailing lists