CVE-2026-64513
Received Received - Intake

KVM CR8 Intercept Update Failure in Linux Kernel

Vulnerability report for CVE-2026-64513, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the β€œuse TPR shadow” VM-execution control is 1 and the β€œvirtualize APIC accesses” and β€œvirtual-interrupt delivery” VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-25
Generated
2026-07-25
AI Q&A
2026-07-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper handling of the TPR_THRESHOLD field in VMX virtualization. When KVM updates the guest's virtual TPR, it may fail to recompute the CR8 intercept correctly if no new interrupts are pending. This leaves a stale TPR_THRESHOLD value, which can cause VM entry failures on older platforms or nested virtualization setups that enforce TPR_THRESHOLD checks.

Detection Guidance

This vulnerability is specific to the Linux kernel's KVM (Kernel-based Virtual Machine) implementation and may not have direct detection commands. However, you can check your kernel version and KVM module status. For systems running affected kernels, monitor for VM entry failures or hardware errors (e.g., error 0x7) during nested virtualization. Use commands like 'uname -a' to check the kernel version and 'lsmod | grep kvm' to verify KVM module status.

Impact Analysis

If you run virtual machines on older hardware or nested virtualization environments like Hyper-V, this vulnerability could cause your VMs to fail during startup or resume with a hardware error (0x7). Modern systems with APICv are less affected as they bypass this check.

Mitigation Strategies

Apply the latest kernel patches from your Linux distribution to resolve this issue. If using nested virtualization, ensure the hypervisor supports APICv (Advanced Programmable Interrupt Controller virtualization) to avoid TPR_THRESHOLD checks. Disable nested virtualization if not required or if the hypervisor does not support APICv.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64513. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart