GPU VulnDB

Database/Kernel, userspace & hypervisor

Xen: guest with a passthrough PCI device exposing an IO port BAR can trigger a hypervisor BUG()

UnscoredCVE-2026-79602Kernel, userspace & hypervisorcurated

Impact

A guest that has been assigned a PCI device with at least one BAR in IO port space can reach a BUG() in Xen. A BUG() in the hypervisor takes down the host, not just the offending guest, so one tenant VM crashes every other VM on that machine. On a GPU host this is expensive: device assignment is exactly how accelerators and SR-IOV NICs are handed to tenants, and a crashed hypervisor means an unplanned reboot of a node whose GPU workloads cannot be live-migrated. XSA-510 does not state that GPUs themselves carry IO port BARs - the trigger is any assigned device that does, which on modern hosts is more often a legacy or bridged function than the accelerator.

Who can reach it

A guest administrator on any VM that already has a PCI device passed through to it. No host credentials needed; the tenant only has to drive the device it was legitimately given.

What to do

Apply the patches published with XSA-510 to the hypervisor and reboot the host into the fixed Xen - Xen patches do not take effect on a running hypervisor. Drain or migrate guests first; VMs holding assigned GPUs cannot be live-migrated and must be stopped. As an interim mitigation, stop assigning PCI devices that expose IO port BARs to untrusted guests.

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.