CVE-2026-64286

Description

A flaw was found in the Linux kernel's Kernel-based Virtual Machine (KVM) for arm64 architecture. The flush_hyp_vcpu() function, responsible for copying the host virtual CPU (vCPU) context, does not properly clear a specific internal pointer (__hyp_running_vcpu). This oversight allows a host to provide a value that is then improperly accessed (dereferenced) at Exception Level 2 (EL2), potentially leading to arbitrary memory access within the hypervisor. This could allow a malicious host to compromise the integrity or availability of the hypervisor.

Statement

This vulnerability is classified as having a Moderate severity because exploitation requires local privileges on an ARM64 system running protected KVM mode, preventing remote unauthenticated attacks. In typical Red Hat Enterprise Linux deployments, Protected KVM is not enabled by default and hardware virtualization requires specific platform support and configuration. Under these conditions, an attacker must already possess sufficient access on the host to interact with the virtualization subsystem, which restricts the potential impact to environments actively executing protected guest instances.

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 Score7N/A8.2
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/AHigh
User InteractionNoneN/ANone
ScopeUnchangedN/AChanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location).

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the untrusted pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands; Modify Memory

If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the untrusted pointer is used in a function call, then the attacker might be able to call arbitrary functions.

Frequently Asked Questions

Want to get errata notifications? Sign up here.