Qubes OS patches AMD CPU flaws enabling qube escape and cross-VM data leaks

Qubes OS has issued Security Bulletin 123 addressing two AMD CPU vulnerabilities disclosed through the Xen Project. XSA-524 involves an out-of-bounds read in AMD IOMMU device table handling on certain EPYC processors, which can allow a malicious qube to compromise the system by writing to arbitrary memory pages. XSA-525 expands known Transient Scheduler Attack vectors to AMD Zen 5 CPUs, including a newly disclosed TSA-Fill variant (CVE-2026-0004), and corrects AMD's prior assurance that Zen 5 was unaffected by earlier TSA-SQ and TSA-L1 variants (CVE-2024-36350, CVE-2024-36357). Both flaws break Qubes OS's core security isolation model between virtual machines.

The Qubes team has released Xen packages version 4.19.6-4 for Qubes 4.3 in dom0 to address both issues. Users must restart dom0 after installation for patches to take effect, and Anti Evil Maid users must reseal their secret passphrase due to PCR18+19 changes from updated Xen binaries. The packages are initially available through security-testing repositories and will migrate to stable channels after community validation, typically within one to two weeks.

Vulnerability details and Xen hypervisor fixes

• XSA-524 / AMD-SB-3060: AMD IOMMU hardware on affected EPYC systems reads beyond the OS/hypervisor-configured device table boundary under specific conditions, interpreting the over-read as valid device configuration data; this enables memory corruption by malicious qubes with a specific device configuration.
• XSA-525 / TSA variants: AMD revised Zen 5 vulnerability status for TSA-SQ and TSA-L1 (CVE-2024-36350, CVE-2024-36357) previously thought unaffected, and disclosed new TSA-Fill (CVE-2026-0004, AMD-SB-3031), all permitting transient execution attacks that leak data across qube boundaries.
• Patch delivery: Xen 4.19.6-4 packages for Qubes 4.3 dom0 contain the mitigations; no Intel CPUs are affected by either advisory.
• Boot chain impact: Xen binary updates modify TPM PCR measurements (PCR18+19), requiring Anti Evil Maid users to reseal their secrets against new PCR values to maintain trusted boot integrity.
• Repository staging: Fixes follow Qubes' standard security-testing-to-stable migration path, with optional early access through temporarily or permanently enabled testing repos per dom0, template, or standalone VM.

Why it matters

These advisories directly stress-test Qubes OS's security-centric value proposition, where VM isolation is the primary defense model; successful exploitation would undermine the entire operating system's architectural guarantees. For the broader Xen and Linux virtualization ecosystem, the Zen 5 TSA corrections signal that AMD's initial CPU security assessments may require ongoing revision, affecting how downstream distributions and cloud operators schedule and communicate embargoed processor mitigations. The IOMMU flaw also highlights continued attack surface in hardware virtualization extensions that hypervisors must carefully validate against vendor errata.