LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54092: KVM: s390: pv: fix index value of replaced ASCE

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel KVM issue affecting s390 protected-virtualization handling. A bad index value can cause KVM to pass wrong addresses during page-table invalidation notifications, which may crash a virtual machine. The provided sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Address during the next kernel maintenance cycle for affected s390 virtualization platforms. Escalate faster where VM availability is business-critical. The source evidence does not justify emergency treatment for unrelated Linux fleets.

Technical view

In s390_replace_asce(), a replacement guest ASCE page should have index set to 0. If not, notifier paths may use incorrect addresses during PTE invalidations. The described consequence is validity intercepts and possible VM crash when the prefix is unmapped.

Likely exposure

Exposure appears limited to Linux systems using KVM on s390 with protected virtualization. General Linux hosts outside that architecture or feature path are not indicated as exposed by the supplied sources.

Exploitation context

The bundle marks KEV as false and provides no cited exploitation reports. Treat this as a reliability and availability risk for affected virtualization hosts, not a confirmed actively exploited vulnerability.

Researcher notes

The public record lacks CVSS, CWE, distro mapping, and exploit evidence. The strongest technical signal is the kernel fix rationale: incorrect ASCE page index can corrupt invalidation notification addresses and trigger guest crash conditions.

Mitigation direction

  • Check vendor or distribution kernel guidance for CVE-2023-54092 updates.
  • Prioritize kernel updates on s390 KVM protected-virtualization hosts.
  • Review the referenced stable kernel commits for fixed branches.
  • Avoid assuming non-s390 Linux systems are affected without vendor confirmation.

Validation and detection

  • Inventory Linux kernels on s390 KVM virtualization hosts.
  • Confirm whether protected virtualization is used on those hosts.
  • Compare deployed kernel versions against vendor advisories and stable fixes.
  • Monitor affected hosts for guest validity intercepts or unexpected VM crashes.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54092 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9d216035d173214cd33712d67d89220ef2283ebf, 81ea65c9aefe100a9ace3082649bd84ae7dd9764, faa2f72cb3569256480c5540d242c84e99965160, faa2f72cb3569256480c5540d242c84e99965160, faa2f72cb3569256480c5540d242c84e99965160, b5477f53e1d4de6191f50748a027251b14952eeb, 63c71e83d5b6ab8adb5fcebef977052048016957, 5.10.137, 5.15.61, 5.18.18, 5.19.2unaffected
LinuxLinux6.0, 0, 5.10.190, 5.15.124, 6.1.43, 6.4.8, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.