cve.bz

CVE-2026-79610 Race Condition

8.8 highEPSS 0.1%

High (8.8). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-79610 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79610?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79610?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79610 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12xen4.17.7+13-g2445b30a44-0+deb12u1DEBIAN-CVE-2026-79610
Debian13xen4.20.4+39-gf1e1321c87-0+deb13u1DEBIAN-CVE-2026-79610
Debian14xen4.20.4+39-gf1e1321c87-1DEBIAN-CVE-2026-79610
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morexenno fix listedUBUNTU-CVE-2026-79610
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morexen4.16.7_16-150400.4.95.1SUSE-SU-2026:4642-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morexen4.17.7_02-150500.3.82.1SUSE-SU-2026:4641-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7xen4.20.4_06-150700.3.49.2SUSE-SU-2026:4942-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5xen4.12.4_76-3.154.1SUSE-SU-2026:4732-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6xen4.18.6_03-150600.3.56.1SUSE-SU-2026:5140-1
openSUSETumbleweedxen4.22.0_06-1.1openSUSE-SU-2026:12138-1
Alpinev3.21xen4.19.6-r2ALPINE-CVE-2026-79610
Alpinev3.22, v3.23xen4.20.4-r2ALPINE-CVE-2026-79610
Alpinev3.24xen4.21.2-r2ALPINE-CVE-2026-79610

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in Xen's grant table handling. A guest repeatedly switching grant table versions (v2→v1→v2) causes status pages to be freed and reallocated, leaving stale pointers that a malicious guest can use to corrupt hypervisor memory, leading to host privilege escalation, information leaks, or DoS. Xen 4.0 onwards is vulnerable (3.4 and earlier not); preconditions: x86 guests permitted grant table v2, multi-vCPU guests only. Fedora's xen 4.20.4 is in the vulnerable range; no fixed release is available yet (XSA-517 patch pending).

Red Hat's mitigation

Set gnttab=max-ver:1 on the hypervisor command line, or max_grant_version=1 in the guest configuration, to prevent use of grant table v2.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-79610.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON