CVE-2026-79610

Published: Oct 13, 2026Modified: Oct 20, 2026

8.8

Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitability: 2.0 / Impact: 6.0

Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary)

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.

Related CWEs

CWE-362

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

The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.

References (3)

https://xenbits.xenproject.org/xsa/advisory-517.html

Source: security@xen.org

http://www.openwall.com/lists/oss-security/2026/10/13/6

Source: af854a3a-2127-422b-91ae-364da2661108

http://xenbits.xen.org/xsa/advisory-517.html

Source: af854a3a-2127-422b-91ae-364da2661108

Timeline

No history available yet.