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.
Project Subscriptions
No data.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Using the "gnttab=max-ver:1" hypervisor command line option will avoid the vulnerability. Using the "max_grant_version=1" guest configuration option for HVM and PVH guests will also avoid the vulnerability.
Tue, 19 May 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Tue, 19 May 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | grant table v2 race in status page mapping | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: XEN
Published:
Updated: 2026-05-19T13:06:51.044Z
Reserved: 2026-01-14T13:07:36.961Z
Link: CVE-2026-23558
No data.
Status : Received
Published: 2026-05-19T14:16:38.960
Modified: 2026-05-19T14:16:38.960
Link: CVE-2026-23558
No data.
OpenCVE Enrichment
No data.
No weakness.