GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KVM x86: stale TPR_THRESHOLD after PPR update causes VM entry failure

CVSS 5.5CVE-2026-64513Kernel, userspace & hypervisorcurated

Impact

In some cases KVM does not recompute the CR8 intercept and TPR_THRESHOLD after the guest's PPR changes. This leaves a stale, high TPR_THRESHOLD in the VMCS, and the VM entry then fails with hardware error 0x7. The record describes this as a guest availability failure, not a privilege escalation or data exposure. Modern bare-metal hosts with APICv (virtual-interrupt delivery) normally do not hit it. Hosts that are exposed are older CPUs without APICv, and KVM running nested under a hypervisor that lacks virtual-interrupt delivery and enforces the check (Hyper-V is the example given). The record does not say whether the failure can reach beyond the affected guest.

Who can reach it

Local to a guest VM: the condition comes from the guest's own interrupt-priority (TPR/PPR) state on a KVM host without virtual-interrupt delivery. No host access is needed, but in practice only older or nested KVM hosts are affected.

What to do

Install a kernel that contains the stable fixes referenced in the record, then drain the guests and reboot each KVM host. Hosts running with APICv enabled on modern CPUs are not exposed as described and can follow the normal kernel update cycle. Nested-KVM setups on Hyper-V and older hosts should go first. The record does not list fixed version numbers.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.