PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-46076 Linux CVE debrief

A logic error in KVM's nested SVM (nSVM) implementation could allow a nested guest (L2) to execute hypercalls with L1 privileges when L1 has not configured interception of VMMCALL instructions. The vulnerability occurs when nested_svm_l2_tlb_flush_enabled() is true and the hypercall is not a supported Hyper-V hypercall. In this scenario, KVM would intercept the VMMCALL but fail to forward it to L1, effectively letting L2 act as L1. The fix synthesizes a #UD (undefined instruction) exception in this case, matching architectural behavior where VMMCALL should #UD when not intercepted.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-27
Original CVE updated
2026-05-27
Advisory published
2026-05-27
Advisory updated
2026-05-27

Who should care

Organizations running nested virtualization workloads on AMD hardware using KVM, cloud providers offering nested virtualization services, and Linux kernel administrators managing multi-tenant virtualized environments

Technical summary

The vulnerability exists in KVM's nested SVM implementation where VMMCALL instructions from an L2 guest could be executed with L1 privileges under specific conditions. When L1 does not intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() returns true, and the hypercall is not a supported Hyper-V hypercall, KVM would intercept but not forward the call to L1. This breaks the expected virtualization boundary. The resolution synthesizes a #UD exception, which is the architecturally correct behavior for unintercepted VMMCALL instructions. The fix has been backported to multiple stable kernel branches as indicated by four separate commits.

Defensive priority

medium

Recommended defensive actions

  • Apply kernel updates from your Linux distribution that include the fix for CVE-2026-46076
  • Verify running kernel version is 6.12.29 or later, or contains the backported fix for your stable branch
  • If running nested virtualization with KVM and AMD SVM, confirm that VMMCALL interception is properly configured for L1 guests
  • Review nested virtualization configurations to ensure L1 guests have appropriate interception controls enabled
  • Monitor for kernel security advisories from your distribution regarding this CVE

Evidence notes

The vulnerability description is derived from the official CVE record and NVD source data. The technical details are based on the kernel commit changelog which describes the specific conditions triggering the bug: L2 active, L1 not intercepting VMMCALL, nested_svm_l2_tlb_flush_enabled() true, and non-Hyper-V hypercall. The fix explicitly raises #UD per architectural specification. Multiple stable kernel branches received backports as evidenced by four separate git.kernel.org stable commits.

Official resources

2026-05-27