CVE-2026-98652

Description

A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) subsystem for the s390 architecture. A missing synchronization lock during status storing operations allows a local user with virtual machine management privileges to trigger a race condition. This flaw can lead to kernel memory corruption or instability, resulting in a Denial of Service (DoS).

Statement

A race in kvm_s390_set_irq_state can execute the Store Status operation lacking kvm srcu protection while another VMM thread replaces or removes KVM memory slots. This can allow kvm_s390_store_status_unloaded to observe stale slot state and creates a plausible use after free candidate in the host kernel, although the patch does not establish a controlled write or proven privilege escalation primitive. For the CVSS the PR:L value reflects that the attacker needs local access to the VM or VCPU file descriptor and must invoke KVM control operations. AC:H reflects the need to race Store Status against memory slot modification. The base impact is host denial of service, while the paranoid score accounts for possible host confidentiality and integrity impact if stale memory slot access becomes exploitable.

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 HatNVDcve.org
Base Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.