GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KVM guest_memfd: failed xarray binding leaves memslot pointing at freed file, use-after-free

UnscoredCVE-2026-99473Kernel, userspace & hypervisorcurated

Impact

If inserting a memslot into a guest_memfd's bindings xarray fails, KVM still reports success and creates the memslot. The memslot then keeps a reference to the guest_memfd after the file is freed, which is a use-after-free in the host kernel. guest_memfd backs confidential-VM memory (SEV-SNP, TDX), so this concerns hosts that run confidential GPU VMs. The trigger depends on the xarray insert failing, for example under memory pressure, and the record does not describe a reliable way to cause that.

Who can reach it

Local. Needs access to /dev/kvm to create guest_memfd memslots, in practice the VMM process. The insert has to fail as well. The record does not describe a path for a guest to trigger it.

What to do

Install a kernel with the stable fix, then drain and reboot each hypervisor host. The record gives no fixed version numbers and no workaround.

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.