Xen XSA-523: malicious guest can read and write any VM's memory, including dom0, via grant copy (CVE-2026-102703, CVE-2026-102704)
Xen hypervisor (and XCP-ng, Qubes OS and other Xen-based platforms)
Sponsored
Brought to you byTinkerer Club
The private club for people who own their servers, run their own AI, and pay $0/month for software.
Two flaws in the Xen hypervisor's grant copy operation let a malicious guest VM read and write arbitrary memory belonging to other domains, including dom0, breaking VM isolation on the host. Xen caches already-validated data during batches of grant copies on the same page, but re-validated it incorrectly: frame numbers and grant references could be mixed up (CVE-2026-102703), and the check limiting copy-by-frame-number to the caller's own memory was misplaced (CVE-2026-102704). Every Xen version from 4.6 onward is vulnerable and there is no mitigation. The Xen Project published patches for xen-unstable through 4.17.x on Nov 3 2026; XCP-ng 8.3 and Qubes OS 4.3 shipped fixed packages that need a host or dom0 reboot, while Debian stable releases were still listed as vulnerable on Nov 4. Found by Anthropic using Claude and validated by Ada Logics; no exploitation has been reported.
Why this severity: Guest-to-host and cross-VM memory read/write with no mitigation; XCP-ng's vendor Vates rates it Critical; no known exploitation
- Started
- Nov 3, 2026
Affected
- Xen 4.6 and later (4.5 and earlier are not vulnerable)
- Xen 4.6 to 4.16: no upstream patch (out of security support)
- Downstream Xen packages until they include the XSA-523 patches (Debian bookworm, trixie and forky listed vulnerable on Nov 4)
Fixed in
- Xen xen-unstable to 4.19.x: xsa523-1/2 patches
- Xen 4.18.x to 4.17.x: xsa523-4.18-1/2 patches
- XCP-ng 8.3: xen-4.17.7-4.2.xcpng8.3 (reboot required)
- Qubes OS 4.3: Xen 4.19.6-3 in dom0 (security-testing first; restart required)
Timeline2
Advisories1
News & write-ups1
Get an email when a new major security incident drops. No spam, unsubscribe any time.
