GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux iommu/vt-d: probe failure frees a PASID table still referenced by live context entries

CVSS 8.2CVE-2026-90241Kernel, userspace & hypervisorcurated

Impact

On Intel IOMMUs in scalable mode, setting up a device with DMA aliases programs a context entry per RID. If the walk fails partway, the probe error path frees the PASID table without first tearing down the context entries already pointing at it, leaving the IOMMU able to walk a Present context entry whose PASID table pointer references freed memory. That is a use-after-free reached by hardware DMA translation, on exactly the machinery that isolates PCIe devices - the same mechanism GPU and NIC passthrough depends on. Reaching it requires a device probe failure, so this is a robustness and isolation fix rather than something a tenant drives directly; the record scores it local with high privileges and a scope change.

Who can reach it

Local, high privilege (AV:L/PR:H) - the actor needs to be able to drive device probe/attach on the host, i.e. host root or an equivalently privileged path. Not reachable from inside a guest or a container without device-management rights.

What to do

Pick up the fix from your distribution's stable kernel (four stable commits are listed) and reboot each affected host; there is no runtime mitigation for an IOMMU teardown-ordering bug. Hosts that do not use Intel VT-d scalable mode are not affected. On GPU nodes this is a drain-and-reboot item that can ride the next kernel maintenance window rather than an emergency.

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.