CVE-2026-89917
Description
A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) for ARM64 architectures. A race condition exists between the Virtual Nested Cache Register (VNCR) Translation Lookaside Buffer (TLB) invalidation and the vcpu_put() function's unmapping of the VNCR page. This time-of-check to time-of-use (TOCTOU) vulnerability can lead to a system crash, resulting in a denial of service.
Statement
A race in KVM arm64 nested virtualization can occur between VNCR TLB invalidation and vcpu_put unmapping of the VNCR fixmap. The race can make both paths observe stale mapping state and can lead to a BUG_ON or a call to vncr_fixmap with cpu -1, causing a host kernel crash or unstable fixmap state. For the CVSS the PR:L is used because a local user or guest workload with access to KVM is needed to create and run the affected vCPU state. The issue is not network reachable and requires an affected arm64 KVM nested virtualization configuration. Impact is at least denial of service via host kernel crash and in the paranoid case may include limited confidentiality or integrity impact because the bug affects host fixmap unmapping state across racing CPUs.
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 | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/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)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability
When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.
Confidentiality,Integrity
Technical Impact: Read Files or Directories; Read Application Data
When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).
Access Control
Technical Impact: Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism
This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.