GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel xen-netback: failed ring mapping leads to double unmap of guest data rings (XSA-532)

UnscoredCVE-2026-99287Kernel, userspace & hypervisorcurated

Impact

When xen-netback fails to map a guest's frontend data rings after one ring is already mapped, it unmaps them but leaves the ring pointers in place, so the cleanup path then unmaps the same rings a second time. The netback backend runs in the host or driver domain and serves every guest's virtual NIC, so trouble in that path affects the host and the guests that share it, not just one VM. The record gives no exploitability assessment beyond the double unmap, and the Xen project tracks it as XSA-532. It only matters on Xen hosts that use the in-kernel netback driver. KVM, ESXi and bare-metal GPU nodes are not affected.

Who can reach it

A guest VM on a Xen host that controls its own netfront ring setup during connection, which can make the backend's ring mapping fail. Needs guest kernel control, not host credentials. Only Xen dom0 or driver domains running xen-netback are exposed.

What to do

Install a kernel with the stable fix in the dom0 or driver domain and reboot the host. Guests have to be migrated off or shut down first. Check XSA-532 on oss-security for distribution and version details. The record names 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.