CVE-2023-54092

KVM: s390: pv: fix index value of replaced ASCE

HIGH

8.8

CVSS Score

Published: December 24, 2025 at 01:06 PM UTC

Updated: October 15, 2026 at 10:17 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

90%

5.10.137 5.15.61 5.18.18 5.19.2 6.063c71e83d5b6ab8adb5fcebef97705204801695781ea65c9aefe100a9ace3082649bd84ae7dd97649d216035d173214cd33712d67d89220ef2283ebfb5477f53e1d4de6191f50748a027251b14952eebfaa2f72cb3569256480c5540d242c84e99965160

Vendor states this is fixed in 017f686bcb536ff23d49c143fdf9d1fd89a9a924 (fixed)

Vendor states this is fixed in 49a2686adddebe1ae76b4d368383208656ef6606 (fixed)

Vendor states this is fixed in 8e635da0e0d3cb45e32fa79b36218fb98281bc10 (fixed)

Vendor states this is fixed in c2fceb59bbda16468bda82b002383bff59de89ab (fixed)

Vendor states this is fixed in f1c7a776338f2ac5e34da40e58fe9f33ea390a5e (fixed)

Vendor states this is fixed in 5.10.190 (unaffected)

Vendor states this is fixed in 5.15.124 (unaffected)

Affected range stops below 5.19, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.0 (unaffected)

Vendor states this is fixed in 6.1.43 (unaffected)

Vendor states this is fixed in 6.4.8 (unaffected)

Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.