GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel iommufd: pointer-sized bound check in veventq read can write past the user buffer

CVSS 7.8CVE-2026-64293Kernel, userspace & hypervisorcurated

Impact

The bound check in the vEVENT read path uses sizeof(hdr) - the size of a pointer - where the rest of the function uses sizeof(*hdr). On 64-bit hosts the two happen to be equal today, so GPU-passthrough and SR-IOV hosts on x86-64 and arm64 are not affected in practice; on 32-bit builds the check under-counts the header by four bytes and the copy writes past the caller's buffer. It is also a latent bug the moment struct iommufd_vevent_header grows beyond a pointer width. iommufd is the interface behind VFIO device assignment, so operators passing GPUs or NICs into VMs should patch it, but should not treat this as an urgent 64-bit exposure.

Who can reach it

Local user holding an iommufd vEVENT queue file descriptor, i.e. a process permitted to drive VFIO device assignment. Exploitable only on 32-bit kernels as the structure stands.

What to do

Apply the stable fix using sizeof(*hdr) and reboot the node. On 64-bit hosts this can ride along with the next scheduled kernel maintenance rather than an emergency window.

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.