The adjustments made for XSA-379 as well as those subsequently becoming XSA-387 still left a race window, when a HVM or PVH guest does a grant table version change from v2 to v1 in parallel with mapping the status page(s) via XENMEM_add_to_physmap. Some of the status pages may then be freed while mappings of them would still be inserted into the guest's secondary (P2M) page tables.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://xenbits.xenproject.org/xsa/advisory-486.html Mitigation, Patch, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/04/28/13 Mailing List, Mitigation, Patch, Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-486.html Mitigation, Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.8 · xenNVD modified 2026-10-14 20:10
Affected (CPE criteria) 1
cpe:2.3:o:xen:xen:*:*:*:*:*:*:*:*
References 3
- https://xenbits.xenproject.org/xsa/advisory-486.html Mitigation, Patch, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/04/28/13 Mailing List, Mitigation, Patch, Third Party Advisory
- http://xenbits.xen.org/xsa/advisory-486.html Mitigation, Patch, Vendor Advisory