CVE-2026-89919
Description
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) component for s390 architecture. This vulnerability occurs due to improper synchronization when handling memory management unit (MMU) locks. Specifically, concurrent operations related to key operations and virtual machine memory limit size can lead to the use of outdated memory mapping information. This can result in memory corruption within the system.
Statement
KVM s390 keyop can read gmap asce outside the mmu_lock read side while a concurrent KVM_S390_VM_MEM_LIMIT_SIZE operation updates the same value under the write side of the lock. This race can make KVM_S390_KEYOP walk memory using a stale address space control value and the upstream description states that this can result in memory corruption. For the CVSS the PR:L is selected because reliable triggering requires local access to KVM ioctls from a user or service that can run or control a VM, but it does not require full host root in many deployments. The issue is not directly network reachable and applies to s390 KVM hosts where these ioctls are available. Impact is at least a local denial of service via memory corruption and in worst case may allow confidentiality or integrity impact or privilege escalation, so it should be reviewed manually.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.