| 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: <2025122407-CVE-2023-54092-91ac@gregkh> Date: Wed, 24 Dec 2025 14:06:49 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-54092: KVM: s390: pv: fix index value of replaced ASCE From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pv: fix index value of replaced ASCE The index field of the struct page corresponding to a guest ASCE should be 0. When replacing the ASCE in s390_replace_asce(), the index of the new ASCE should also be set to 0. Having the wrong index might lead to the wrong addresses being passed around when notifying pte invalidations, and eventually to validity intercepts (VM crash) if the prefix gets unmapped and the notifier gets called with the wrong address. The Linux kernel CVE team has assigned CVE-2023-54092 to this issue. Affected and fixed versions =========================== Issue introduced in 5.10.137 with commit 9d216035d173214cd33712d67d89220ef2283ebf and fixed in 5.10.190 with commit 8e635da0e0d3cb45e32fa79b36218fb98281bc10 Issue introduced in 5.15.61 with commit 81ea65c9aefe100a9ace3082649bd84ae7dd9764 and fixed in 5.15.124 with commit 49a2686adddebe1ae76b4d368383208656ef6606 Issue introduced in 6.0 with commit faa2f72cb3569256480c5540d242c84e99965160 and fixed in 6.1.43 with commit 017f686bcb536ff23d49c143fdf9d1fd89a9a924 Issue introduced in 6.0 with commit faa2f72cb3569256480c5540d242c84e99965160 and fixed in 6.4.8 with commit f1c7a776338f2ac5e34da40e58fe9f33ea390a5e Issue introduced in 6.0 with commit faa2f72cb3569256480c5540d242c84e99965160 and fixed in 6.5 with commit c2fceb59bbda16468bda82b002383bff59de89ab Issue introduced in 5.18.18 with commit b5477f53e1d4de6191f50748a027251b14952eeb Issue introduced in 5.19.2 with commit 63c71e83d5b6ab8adb5fcebef977052048016957 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-2023-54092 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/s390/mm/gmap.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/8e635da0e0d3cb45e32fa79b36218fb98281bc10 https://git.kernel.org/stable/c/49a2686adddebe1ae76b4d368383208656ef6606 https://git.kernel.org/stable/c/017f686bcb536ff23d49c143fdf9d1fd89a9a924 https://git.kernel.org/stable/c/f1c7a776338f2ac5e34da40e58fe9f33ea390a5e https://git.kernel.org/stable/c/c2fceb59bbda16468bda82b002383bff59de89ab
Powered by blists - more mailing lists