CVE-2026-46076: KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1
In the Linux kernel, the following vulnerability has been resolved:
KVM: nSVM: Raise #UD if unhandled VMMCALL isn't intercepted by L1
Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nestedsvml2tlbflushenabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1.
The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it's not intercepted.
Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining "single" stub will soon be dropped as well.
[sean: rewrite changelog and comment, tag for stable, remove defunct stubs]
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46076?
CVE-2026-46076 has a severity rating of high with a score of 7.9.
How do I fix CVE-2026-46076?
To fix CVE-2026-46076, you need to apply the available patch provided for the Linux kernel.
What impact does CVE-2026-46076 have on my system?
CVE-2026-46076 can lead to denial of service or stability issues in systems using nested virtualization.
Is CVE-2026-46076 exploitable remotely?
CVE-2026-46076 is considered to have local exploitability, requiring access to the virtual machine.
What software is affected by CVE-2026-46076?
CVE-2026-46076 affects the Linux kernel, specifically in the KVM subsystem for nested virtualization.