GPU VulnDB

Database/Kernel, userspace & hypervisor

Xen: race in viridian reference TSC page mapping frees a page still live in the guest p2m

CVSS 9.8CVE-2025-58143Kernel, userspace & hypervisorcurated

Impact

A race in the mapping of the viridian reference TSC page lets a guest get Xen to free a page that is still present in the guest physical-to-machine (p2m) tables. This is the serious member of XSA-472: a freed page that remains guest-accessible is a path to writing memory the guest no longer owns, so host compromise or cross-guest impact cannot be ruled out, not just a crash. On a multi-tenant GPU host that means the isolation boundary between tenants sharing the machine - and the accelerators and fabric behind it - is in question. Treat this one as more than availability, even though the advisory stops short of a demonstrated escape.

Who can reach it

A local administrator inside an HVM guest with viridian enlightenments enabled, racing the hypervisor. No host credentials needed.

What to do

Patch the hypervisor per XSA-472 and reboot each host, draining or live-migrating guests first; this one is worth scheduling ahead of the two NULL dereferences in the same advisory. Where a window cannot be found quickly, disable viridian enlightenments on guests you do not fully trust.

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.