GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KVM TDX: Notify VM exit accepted for TDX guests but never enabled in the TD VMCS

UnscoredCVE-2026-99338Kernel, userspace & hypervisorcurated

Impact

KVM reports KVM_CAP_X86_NOTIFY_VMEXIT for TDX guests based on hardware support, but never calls the TDX module to set NOTIFY_VM_EXITING and the notify window, so enabling it silently does nothing. Notify VM exit (instruction timeout) is the control that lets the host get the CPU back from a guest stuck in a state that produces no VM exits. With it missing, a TDX guest the operator thinks is covered is not, which on a shared confidential-computing host means the expected protection of the physical CPU against a misbehaving guest is absent.

Who can reach it

A tenant controlling code in a TDX guest on a host whose VMM enables KVM_CAP_X86_NOTIFY_VMEXIT. No host-side authentication needed.

What to do

Install a kernel with the stable fix (commits linked) on TDX hosts, then migrate or drain guests and reboot. The record does not give fixed version numbers.

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.