GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KVM SVM: nested vmcb01/vmcb02 ASID tracking lets two vCPUs share one ASID on a pCPU

UnscoredCVE-2026-99346Kernel, userspace & hypervisorcurated

Impact

With nested virtualization on AMD, vmcb01 and vmcb02 share an ASID but track their last pCPU separately. After a migration between pCPUs, one VMCB can reuse an ASID on the old pCPU that another vCPU has since been given, so two vCPUs run with the same ASID on the same physical CPU. ASIDs tag TLB entries, so sharing one breaks the TLB isolation between those vCPUs, and nothing in the record limits them to the same VM. On a multi-tenant AMD host that is a guest isolation failure.

Who can reach it

Requires a guest using nested SVM on an AMD host, plus vCPU scheduling across pCPUs. Triggered from inside a tenant guest with no host authentication. The record does not describe a targeted exploit.

What to do

Install a kernel with the stable fix (commits linked) on AMD KVM hosts, then migrate or drain guests and reboot. Disabling nested SVM for tenant guests (kvm_amd nested=0) removes the path. The record does not give fixed versions.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.