GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel vhost-vdpa: ASID equal to ngroups passes validation, giving an out-of-bounds write in vdpa_sim

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

Impact

Group bound checks were scattered across vdpa parent drivers; consolidating them in vhost_vdpa exposed that vdpa_sim accepted an address-space id assigned to a group index equal to ngroups, one past the end, producing an out-of-bounds write. The affected write is in the vdpa simulator, which is a development and test parent driver, not something a production GPU fleet normally loads - so for most operators the real content here is the missing validation in the common vhost_vdpa path plus a kernel heap write on any host where vdpa_sim* is present. Where vhost-vdpa is used to give tenant VMs accelerated networking, the ioctl surface belongs to the VMM, so the attacker is a local user or a tenant's VMM process, and a successful write is host-level compromise on a node holding other tenants' GPUs.

Who can reach it

Local user with access to a vhost-vdpa device node (/dev/vhost-vdpa-N), typically the VMM process or a privileged networking component. The out-of-bounds write specifically requires the vdpa_sim parent driver to be in use; check with lsmod | grep vdpa.

What to do

Update to a stable kernel with the consolidated bound checks (four branches carry backports) and reboot the node. Before scheduling that window, check whether vdpa_sim/vdpa_sim_net is loaded at all - on a production fleet it usually is not, and blacklisting it removes the out-of-bounds write without a reboot, leaving only the hardening part of the change pending.

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.