CVE-2026-89932

Description

A flaw was found in the Kernel-based Virtual Machine (KVM) subsystem. This vulnerability occurs when KVM reuses a Virtual Processor ID (VPID) without properly flushing Translation Lookaside Buffer (TLB) entries. A malicious guest virtual machine (VM) could potentially exploit this to access stale TLB entries from a previous VM or virtual CPU, leading to information disclosure or privilege escalation.

Statement

This vulnerability is rated as an Important impact because the failure to invalidate stale hardware translation cache entries during nested VMX transitions can allow an L1 or L2 guest to access memory mappings belonging to another virtual context. Although this flaw allows potential cross-VM data exposure or privilege elevation, exploitation is restricted to systems where nested Intel virtualization is explicitly utilized. Additionally, successful triggering depends on specific hypervisor state transitions where nested VMX is disabled and re-enabled, and the host reallocates an un-flushed processor identifier. Standard virtualized environments that do not configure or expose nested hardware virtualization are unaffected by this flaw.

Mitigation

Disable nested virtualization on Intel KVM hosts if nested virtual machines are not required.

1. Create or modify the module configuration file to disable the nested feature:
# echo "options kvm_intel nested=0" > /etc/modprobe.d/kvm_intel.conf

2. Apply the configuration by removing and reloading the kvm_intel module:
# modprobe -r kvm_intel
# modprobe kvm_intel

Warning: Reloading the kvm_intel kernel module requires stopping all active virtual machines on the host. If virtual machines cannot be stopped immediately, reboot the host system to apply the configuration.

Caveat: Disabling nested virtualization prevents virtual machines from running their own nested hypervisors (L2 guests).

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score8.8N/A8.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeChangedN/AChanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data

If the cache is accessible to unauthorized actors, attackers can read the cache and obtain this sensitive information.

Frequently Asked Questions

Want to get errata notifications? Sign up here.