CVE-2026-64604

CVE CVE-2026-64604EUVD EUVD-2026-53790Published 2026-08-06T07:13:55.000ZLast changed 2026-08-06T17:37:50.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode When updating CR8 intercepts, get vmcs12 if and only if the vCPU is in guest mode so that a future change can have update CR8 intercepts during vCPU creation, without running afoul of get_vmcs12()'s lockdep assertion. ------------[ cut here ]------------ debug_locks && !(lock_is_held(&(&vcpu->mutex)->dep_map) || !refcount_read(&vcpu->kvm->users_count)) WARNING: arch/x86/kvm/vmx/nested.h:61 at get_vmcs12 arch/x86/kvm/vmx/nested.h:60 [inline], CPU#0: syz.2.19/5879 WARNING: arch/x86/kvm/vmx/nested.h:61 at vmx_update_cr8_intercept+0x3de/0x4e0 arch/x86/kvm/vmx/vmx.c:6879, CPU#0: syz.2.19/5879 Modules linked in: CPU: 0 UID: 0 PID: 5879 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:get_vmcs12 arch/x86/kvm/vmx/nested.h:60 [inline] RIP: 0010:vmx_update_cr8_intercept+0x3de/0x4e0 arch/x86/kvm/vmx/vmx.c:6879 Call Trace: <TASK> apic_update_ppr arch/x86/kvm/lapic.c:984 [inline] kvm_lapic_reset+0x1c24/0x2980 arch/x86/kvm/lapic.c:3023 kvm_vcpu_reset+0x44c/0x1bf0 arch/x86/kvm/x86.c:12986 kvm_arch_vcpu_create+0x746/0x8b0 arch/x86/kvm/x86.c:12847 kvm_vm_ioctl_create_vcpu+0x428/0x930 virt/kvm/kvm_main.c:4201 kvm_vm_ioctl+0x893/0xd50 virt/kvm/kvm_main.c:5159 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> No functional change intended.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 0; a7c0b07d570848e50fce4d31ac01313484d6b844 <3dcfb04dd43b16fa1240fc6487fff578ad57264c; patch: 7.2-rc1; patch: 6.6.145; patch: 7.1.4; patch: 6.12.96; patch: 5.10.261; patch: 6.1.178; a7c0b07d570848e50fce4d31ac01313484d6b844 <ffaaff82336db84e9b58e7a3e81c2fd64e05ed7a; a7c0b07d570848e50fce4d31ac01313484d6b844 <7ef78d71ca713d8c00f7c34ddcf276c808143f77; patch: 6.18.39; a7c0b07d570848e50fce4d31ac01313484d6b844 <9a21f1defd96c6301c5fb462a78eb51b191bd2dd; 3.18; a7c0b07d570848e50fce4d31ac01313484d6b844 <258ec63c0f281bf7b50f9de67c8e93b5b7be5ed4; patch: 5.15.212; a7c0b07d570848e50fce4d31ac01313484d6b844 <db8407b9fd06d857a4a5e8bcff1d086d13007711; a7c0b07d570848e50fce4d31ac01313484d6b844 <c7cd3605244c924249dea32632e1bc3e89bda543; a7c0b07d570848e50fce4d31ac01313484d6b844 <570af5db081b87374594a00711ac5760d2ea6844

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.