GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel KVM: spurious userspace exit when checking nested events can kill the guest

CVSS 5.5CVE-2026-43265Kernel, userspace & hypervisorcurated

Impact

If a vCPU leaves a blocking state while L2 is active and the nested-event check returns -EBUSY, KVM exits to userspace with what is usually KVM_EXIT_UNKNOWN. The VMM has no sensible way to handle that and the VM typically dies. Reaching the state requires userspace to have stuffed MP_STATE or injected events into the vCPU - something a VMM can do, and something a guest-adjacent control path can be coaxed into. For a GPU cloud that hands tenants nested virtualization or runs confidential VMs, the result is an availability problem: the guest is lost, not the host. The host kernel keeps running, so this is a tenant-VM crash rather than a node-level outage.

Who can reach it

Local, through the KVM ioctl interface - a process holding /dev/kvm or the VMM itself must set the vCPU into the odd state. Not reachable from inside an unprivileged guest on its own, and not reachable over the network.

What to do

Pick up the stable kernel fix and restart the affected VMs; because the change is in the kvm module, a node can be remediated by draining the guests and reloading kvm/kvm_intel rather than a full reboot in some configurations, but the practical path for most fleets is a kernel update and node reboot. No configuration workaround is described in the fix.

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.