CVE-2026-98716

What it actually does

Incorrect MSR permission bitmap selection in KVM SVM nested virtualization allows L2 guests to access MSRs that should be intercepted when L1 configures selective interception, bypassing the intended authorization checks on MSR accesses.

Why it matters to the business

Nested virtualization environments on AMD processors may experience unauthorized register access by guest workloads, increasing risk of VM escape or privilege escalation within virtualized infrastructure and requiring urgent kernel updates to maintain isolation guarantees.

How an attack unfolds

An attacker with control of an L2 guest configures MSR access patterns that exploit the mismatch between the active VMCB bitmap and the assumed vmcb02 bitmap; when L1 enables selective MSR interception, the wrong bitmap is consulted, permitting the L2 guest to read or write protected MSRs that should trigger exits to L0.

How to fix it

Apply the upstream Linux kernel patch that selects the active VMCB's MSR bitmap for interception checks; rebuild and deploy updated kernels to all affected hosts running KVM on AMD processors.

How to confirm the fix worked

Confirm the fix by inspecting the KVM SVM MSR bitmap selection logic in the running kernel source or binary for use of the active VMCB pointer instead of a hardcoded vmcb02 reference; test nested guest MSR interception behavior under L1 selective interception.

Typical attack path

1. Compromise or control an L2 nested guest on an AMD SVM host
2. Trigger L1 hypervisor to enable selective MSR interception via msrpm01/msrpm12 merge
3. Issue MSR read/write operations that rely on the incorrect active bitmap
4. Bypass interception and access privileged MSRs directly from L2
5. Escalate to impact L0 host or other guests via MSR side effects

How to detect it

Search hypervisor and guest kernel logs for anomalous MSR access patterns or missing VM exits during nested virtualization; examine KVM SVM code paths handling L1/L2 MSR bitmap merges for signs of prior exploitation via unexpected guest behavior or crashes.

What your security team should do

• Prioritize kernel updates on all AMD-based KVM hosts within the next maintenance window
• Audit nested virtualization configurations and disable if not required
• Monitor for new kernel releases containing the described MSR bitmap correction
• Review hypervisor logs for unexpected MSR exit patterns after patching