GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux xen-netback: multicast list freed during disconnect while TX/RX processing may still use it (XSA-527)

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

Impact

The Xen network backend driver in the dom0 or driver-domain kernel freed a guest's multicast address list without locking or RCU while transmit and receive processing could still be looking it up or changing it. This is a race that can lead to use of freed memory in the backend domain. The vector is scope-changed, so a guest-side actor could affect the domain that serves networking to every guest on the host, which matters on a shared Xen host carrying several tenants. The record does not describe a working exploit, and it gives no detail beyond the fix and the Xen advisory number.

Who can reach it

A low-privileged actor on a Xen host with a paravirtual network interface served by xen-netback, most likely a guest driving its netfront connect and disconnect sequence. The attack complexity is high because a race must be won. Only Xen deployments that run netback are affected. KVM, ESXi and bare-metal GPU nodes do not use this code.

What to do

Install a kernel carrying the stable fix in the dom0 or driver domain, then reboot that domain. That restarts or interrupts every guest on the host, so plan to live-migrate guests off first or schedule a full host window. The record does not name fixed kernel versions. Check your distribution's kernel advisory and XSA-527 from the Xen project.

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.