GHSA-p4h6-6vf5-jwcw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessControl a guest VM on shared Xen host
-
ExploitHold read-only grant mapping from another domain
-
ExecutionIssue GNTTABOP_cache_flush invalidate-without-clean
-
ImpactCorrupt granting domain's memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer underflow checks
|
| Exploitation Conditions | Requires the attacker to already control a guest domain on a Xen host that holds a read-only grant mapping shared from another domain via the grant table interface; the attacker then invokes GNTTABOP_cache_flush using invalidate-without-clean against that read-only mapping. Exploitation is limited to multi-domain/multi-tenant Xen deployments that use inter-domain memory sharing, and needs code execution inside a guest rather than any network access. Authentication requirements are not cleanly confirmed because the supplied CVSS vector (PR:N) appears to belong to the sibling CVE; in practice a running, attacker-controlled guest domain is the prerequisite. |
| Impact | Signals point to a moderate, situational priority rather than a top-tier emergency. The input CVSS base score of 7.5 and its vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) do NOT match this specific CVE: that vector describes an availability/denial-of-service impact and, together with the CWE-191 (integer underflow) and 'Denial Of Service'/'Integer Overflow' tags, clearly corresponds to the sibling issue CVE-2026-102699 in the same shared Xen record. CVE-2026-102702 is instead a memory-INTEGRITY flaw: a guest can issue GNTTABOP_cache_flush with invalidate-without-clean against a read-only grant mapping and corrupt another domain's memory - an integrity (I) impact, not the availability (A:H) shown. Exploitation probability is low (EPSS 0.15%, 3rd percentile), there is no CISA KEV listing and no public exploit identified, so this is not evidence of active or widespread exploitation. Realistically the attacker must already control a guest VM on a shared Xen host and hold a read-only inter-domain grant mapping, which confines risk to multi-tenant virtualization environments. Net: a credible cross-domain memory-corruption bug worth patching on shared hypervisors, but the provided CVSS vector should be treated as mislabeled and verified against Xen advisory XSA-519 before being used for prioritization. |
| Exploit ScenarioDerived | A tenant who controls a guest domain on a shared Xen host maps memory that another domain granted to it read-only, then issues a GNTTABOP_cache_flush invalidate-without-clean operation against that mapping, corrupting the granting domain's memory contents. No public exploit code has been identified. Because the attacker must execute hypercalls from inside a guest, exploitation is local to the host rather than network-remote despite the input vector's AV:N. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 20, 2026
A guest domain on a Xen hypervisor can corrupt memory belonging to another domain by issuing GNTTABOP_cache_flush with invalidate-without-clean semantics against a read-only grant mapping it was given, because the hypervisor does not reject that operation/mapping combination. Only multi-tenant or disaggregated Xen deployments that actually share pages between domains through the grant table are exposed, and the attacker must already be running code in a guest (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N). Impact is silent integrity corruption of the granting domain's data rather than a crash or leak; EPSS is 0.15% (3rd percentile) and no public exploit identified at time of analysis.
Earlier versions of this analysis (1)
Incorrectly unchecked cache-flush operations on Arm-based Xen hypervisors let an unprivileged guest corrupt memory that another domain has exposed through a read-only grant mapping, with privilege escalation and information disclosure not ruled out, as detailed in Xen Security Advisory XSA-519 (CVE-2026-102702). The flaw affects Xen 4.5 through 4.21.x/unstable on Arm only; x86 systems are explicitly not vulnerable. Under the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:L the attacker must already control a local low-privileged guest and must hold a suitable cross-domain read-only grant mapping, and no public exploit code or CISA KEV confirmation exists at time of analysis.
RemediationAI
Apply the Xen patches published with XSA-519 (https://xenbits.xenproject.org/xsa/advisory-519.html), which is the vendor fix for both issues in this advisory; the supplied data does not state exact patched version numbers, so confirm the minimum fixed revision for your branch in that advisory before upgrading and reboot the hypervisor, since Xen hypervisor fixes only take effect on a fresh boot. If patching must be deferred, the effective compensating control is to remove the trust boundary the bug crosses: avoid sharing read-only grant mappings from one security domain to another, and keep untrusted guests off hosts that run disaggregated backends or stub domains - the trade-off is loss of the driver-domain/stub-domain isolation model and reduced consolidation density. Restricting GNTTABOP_cache_flush outright is not a practical workaround because it breaks legitimate cache maintenance for non-coherent DMA on Arm and can cause data corruption in the backends themselves, and reverting the XSA-437 fixes instead reintroduces the integer-overflow/underflow denial-of-service issues tracked as CVE-2023-34321 and CVE-2026-102699.
Affected ProductsAI
Xen hypervisor releases that expose the GNTTABOP_cache_flush grant-table operation and predate the fixes published in Xen security advisory XSA-519 (https://xenbits.xenproject.org/xsa/advisory-519.html), referenced from the NVD record for CVE-2026-102702; the advisory is the authoritative source for the exact version matrix, since the supplied data includes no CPE strings. Practical exposure is limited to hosts where grant-table memory sharing actually crosses security boundaries - multi-tenant hosts, disaggregated/driver-domain architectures and stub-domain deployments - with 64-bit Arm systems of particular interest because explicit cache maintenance is required there. Single-tenant hosts where all guests on a box are equally trusted are affected by the bug but carry little real risk.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Xen's grant table is the shared-memory primitive that lets one domain expose pages to another - it underpins split block/net drivers, stub domains and disaggregated driver setups. GNTTABOP_cache_flush is a hypercall that asks Xen to clean and/or invalidate cache lines for a grant-mapped page, which matters most on non-coherent 64-bit Arm hardware where a guest must manage cache state for pages it does not own. An 'invalidate-without-clean' flush discards cache lines without writing them back, so it is only safe against memory whose dirty contents the issuer is entitled to throw away. This record documents the case where Xen fails to restrict that operation against read-only grant mappings: a guest holding a read-only mapping can drop another domain's uncommitted dirty data, so the granting domain's page ends up with stale or garbage content. Note that the CWE-191 (integer underflow) tag attached to the CVE record describes the companion issue in the same advisory - the underflow in the cache-flush length calculation introduced by XSA-437 (CVE-2023-34321), tracked separately as CVE-2026-102699 - rather than the root cause here, which is a missing validation/permission check between hypercall semantics and mapping permissions.
Know when Xen gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Triggered by hypercall from a controlled guest (AV:L, PR:L), corrupts another domain's read-only granted memory crossing a security boundary (S:C, I:H), with no confidentiality or stated availability impact.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Description PRE-NVD
Executive ViewAI
A high-severity integrity flaw in the Xen hypervisor lets a guest virtual machine silently corrupt data held by another guest on the same host, without causing a crash or alerting the victim. Only multi-tenant or disaggregated Xen environments that share memory pages between domains via the grant table are exposed, which typically means cloud, hosting, and consolidated virtualization estates rather than single-tenant internal labs. Leadership should care because corruption is silent and no vendor patch exists yet, so affected tenants' data and the trust placed in shared infrastructure are at risk until mitigations or a fix are in place.
No vendor-released patch identified at time of analysis. Interim mitigations: segregate tenants onto dedicated Xen hosts or pools; eliminate cross-domain grant-table page sharing, particularly read-only mappings, between domains that do not fully trust each other; restrict guest privileges and grant-table operations available to untrusted guests; enable integrity monitoring and checksums on data shared across domains to detect silent corruption; monitor the Xen project security advisory feed for a fixed release and apply it immediately when available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and
The Floppy Disk Controller (FDC) in QEMU, as used in Xen 4.5.x and earlier and KVM, allows local guest users to cause a
A statement in the System Programming Guide of the Intel 64 and IA-32 Architectures Software Developer's Manual (SDM) wa
The AdSanity plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'aj
An issue was discovered in Xen through 4.9.x allowing x86 PV guest OS users to cause a denial of service (unbounded recu
An issue (known as XSA-212) was discovered in Xen, with fixes available for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. Rated
The C+ mode offload emulation in the RTL8139 network card device model in QEMU, as used in Xen 4.5.x and earlier, allows
Xen, when used on a system providing PV backends, allows local guest OS administrators to cause a denial of service (hos
x86 pv: Insufficient care with non-coherent mappings T[his CNA information record relates to multiple CVEs; the text exp
Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obt
Xen through 4.8.x mishandles page transfer, which allows guest OS users to obtain privileged host OS access, aka XSA-217
The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_h
EUVD-2026-98831
NVD
CVE.org
EPSS
Exploit-DB