GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KVM TDX: Bus Lock VM exit reported as enabled for TDX guests but never programmed

UnscoredCVE-2026-99337Kernel, userspace & hypervisorcurated

Impact

On Intel TDX hosts, KVM advertises KVM_BUS_LOCK_DETECTION_EXIT based on hardware capability alone, so a VMM can enable it for a TDX guest and get no error, but the TD VMCS control is never set and no exit handler exists. The operator believes bus-lock detection (and any rate limiting built on it) is active for confidential guests when it is not. On a shared host, that removes the control meant to stop one guest's bus locks from degrading memory performance for co-tenant VMs on the same socket. The record describes a missing feature, not memory corruption.

Who can reach it

A tenant running code inside a TDX guest on a host whose VMM enables bus-lock detection. No host authentication needed beyond owning the guest.

What to do

Install a kernel carrying the stable fix (commits linked) on TDX hypervisor hosts, then live-migrate or drain guests and reboot each host. Until then, do not rely on bus-lock detection for TDX guests. The record does not list 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.