CVE-2026-79610

grant-table: double version change race

Published Oct 13, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain
other grant table operations. Sadly a v2 -> v1 -> v2 change has yet
another effect which wasn't accounted for: During the first change, status
pages would be freed. During the second change they would be allocated
again. Hence across the full pair of change the addresses of the status
pages may change, rendering stale previously calculated pointers into the
status array.

Analysis

AI-generated

Technical impact

The vulnerability occurs when the Xen grant table undergoes a sequence of version changes (v2 to v1 to v2). During the first downgrade, status pages are freed. After the subsequent upgrade, these pages are reallocated, causing the addresses of the status pages to change. This race condition leads to stale, dangling pointers in the status array, which can result in memory corruption and potential denial‑of‑service or uncontrolled execution within the hypervisor. The weakness is a classic race condition (CWE‑362).

Affected Systems

The flaw affects the Xen hypervisor shipped by the Xen Project. No specific version numbers were disclosed in the advisory, so all recent Xen distributions that implement the grant‑table versioning scheme may be vulnerable until a patch is released.

Risk and Exploitability

The CVSS score is 8.8, and the EPSS score indicates a very low but non‑zero exploitation probability (<1%). The vulnerability resides in privileged hypervisor code, so any successful exploitation would grant host control. The likely attack vector is a guest that can trigger the contested version transitions; this is inferred from the description. The attack requires a guest that can trigger the version changes, which is feasible for privileged guests or an attacker that can compromise the hypervisor’s guest configuration. While the vulnerability is not listed in CISA's KEV catalog and no public exploit is known, the race condition and dangling pointer combination warrants a high exploitation risk in environments using grant tables extensively.

Remediation

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 guests will also avoid the vulnerability.


OpenCVE Recommended Actions

  • Configure the Xen hypervisor with the command‑line option "gnttab=max-ver:1" to restrict grant table operations to version 1, eliminating the race condition.
  • For each guest, set the configuration option "max_grant_version=1" to prevent it from requesting version 2 grant table changes.
  • Monitor Xen advisory channels and apply the vendor patch as soon as a fix becomes available to ensure the hypervisor no longer contains the susceptible code.

Generated by OpenCVE AI on October 23, 2026 at 07:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4818-1 xen security update
Debian DLA Debian DLA DLA-4881-1 xen security update
Debian DSA Debian DSA DSA-6571-1 xen security update
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Xen
Xen xen
Vendors & Products Xen
Xen xen
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Description XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second change they would be allocated again. Hence across the full pair of change the addresses of the status pages may change, rendering stale previously calculated pointers into the status array.
Title grant-table: double version change race
References
Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Sources

Status
PUBLISHED
Assigner
XEN
Published
Updated
Oct 20, 2026, 5:33 PM
Reserved
Aug 25, 2026, 7:35 AM
Status
Awaiting Analysis
Published
Oct 13, 2026, 4:17 PM
Modified
Oct 20, 2026, 6:17 PM