CVE-2026-74516: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active

Published Aug 15, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active

Always update x2APIC MSR intercepts for L1 when AVIC is deactivated, even if L2 is active and KVM is using a separate MSR bitmap to run L2. If AVIC is fully enabled prior to running L2, and is then inhibited while L2 is active (for a VM-scoped inhibit), then KVM will run L1 with AVIC disabled, but with x2APIC MSR intercepts disabled, i.e. will allow L1 to read most of the host's APIC state, send arbitrary interrupts, change task priority, and ultimately trivially DoS the host.

E.g. sending a self-IPI in L1 on HYPERVREENLIGHTENMENTVECTOR, 0xee, with CONFIGHYPERV=n in the host kernel as a "safe" PoC, yields:

Spurious interrupt (vector 0xee) on CPU#425. Acked

And hacking KVM to abuse kvmsetpostedintrwakeuphandler() to register a handler and WARN on POSTEDINTRWAKEUPVECTOR yields:

------------[ cut here ]------------ WARNING: arch/x86/kvm/svm/svm.c:5594 at piwakeuphandler+0x9/0x10 [kvmamd], CPU#156: nestedx2apict/316940 CPU: 156 UID: 0 PID: 316940 Comm: nestedx2apict Tainted: G S U Tainted: [S]=CPUOUTOFSPEC, [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20260209.0-0 02/09/2026 RIP: 0010:piwakeuphandler+0x9/0x10 [kvmamd] Call Trace: <IRQ> sysveckvmpostedintrwakeupipi+0x64/0x80 </IRQ> <TASK> asmsysveckvmpostedintrwakeupipi+0x1a/0x20 RIP: 0010:vcpurun+0x1430/0x1e40 [kvm] kvmarchvcpuioctlrun+0x2c1/0x600 [kvm] kvmvcpuioctl+0x580/0x6b0 [kvm] sesysioctl+0x6d/0xb0 dosyscall64+0x10a/0x480 entrySYSCALL64afterhwframe+0x4b/0x53 RIP: 0033:0x46ff4b </TASK> ---[ end trace 0000000000000000 ]---

Affected Software

1 affected component
Linux Linux kernel

Event History

Aug 15, 2026
CVE Published
via MITRE·12:27 PM
Data Sourced
via MITRE·12:27 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-74516?

The severity of CVE-2026-74516 is rated as 57.

2

How do I fix CVE-2026-74516?

To fix CVE-2026-74516, update to the latest version of the Linux kernel where the vulnerability has been resolved.

3

What systems are affected by CVE-2026-74516?

CVE-2026-74516 affects systems running the Linux kernel that utilize KVM with SVM.

4

What is the impact of CVE-2026-74516?

The impact of CVE-2026-74516 can lead to improper handling of x2APIC MSR intercepts in KVM, which could affect virtualization stability.

5

Is there a workaround for CVE-2026-74516?

There is no specific workaround recommended for CVE-2026-74516, and updating the kernel is the best mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203