ZeroHour
oss-securitypublished ()ingested 1
Part of a story covered by 4 sources: “Xen publishes XSA-510 through XSA-513 (v3): four advisories covering hypervisor crashes, data exposure, oxenstored resource exhaustion, and Tapdisk out-of-bounds flaws” — merged summary and timeline →

Xen Security Advisory 510 v3 (CVE-2026-79602) - x86: improper handling of HVM emulation return codes

AI summary · glm-5.3-flash

Xen Project released XSA-510 (CVE-2026-79602) fixing mishandled HVM emulation return codes that let PCI-passthrough guests crash Xen.

Xen Security Advisory 510 v3 publicly discloses CVE-2026-79602, improper handling of HVM emulation return codes in the Xen hypervisor on x86. A guest with an assigned PCI device that has at least one BAR in the IO port space can trigger a BUG() in Xen. The advisory was released publicly as version 3.

  • CVE-2026-79602 assigned to the HVM emulation return-code flaw
  • Triggered via PCI device passthrough with an IO port space BAR
  • Guest-triggerable BUG() crash condition in Xen on x86
  • Published as public Xen Security Advisory XSA-510 v3
ProductsXen
OrganizationsXen Project

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-79602
Guest-triggerable hypervisor DoS in Xen via PCI passthrough I/O port BARs

Xen's x86 hypervisor improperly handles return codes in its HVM instruction emulation path, and a guest that has been assigned a PCI device (via passthrough) whose BAR (Base Address Register) is mapped into the I/O port address space can trigger a BUG() in the hypervisor, as documented in Xen Security Advisory 510 (CVE-2026-79602). An attacker controlling such a guest — typically a guest administrator on a host using PCI device assignment — can deliberately trigger the flaw through guest actions that go through the emulation path. The outcome is a denial of service: the BUG() crashes the host's hypervisor, disrupting all guests on that physical machine; the advisory does not indicate privilege escalation or data exposure. Only x86 Xen deployments that assign PCI devices to guests where an assigned device has an I/O port BAR are affected; hosts without passthrough, or with MMIO-only devices, are not exposed. There is no public proof-of-concept, the issue is not in CISA KEV, and EPSS estimates only a 0.2% 30-day exploitation probability (7th percentile), so no exploitation is currently known.

Do: Update the Xen hypervisor per XSA-510 v3 (consult the advisory for the fixed version ranges applicable to your supported release), scheduling host reboots as required. Until patched, audit guest configurations for PCI device passthrough (e.g., 'xl pci-list' and guest device assignments), identify assigned devices with I/O port BARs using 'lspci -v', and avoid assigning such devices to guests or limit those guests to trusted administrators. Since the impact is a guest-triggered host crash, prioritizing patching on hosts that use device assignment is the most efficient remediation path.

8.8<1%
  • Xen Project Xen hypervisor (x86) — HVM guests with PCI device assignment where the assigned device has a BAR in I/O port space
large~tens of thousands of hosts worldwide (estimate)
Full article

Posted by Xen . org security team on Sep 08 Xen Security Advisory CVE-2026-79602 / XSA-510 version 3 x86: improper handling of HVM emulation return codes UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= A guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen. IMPACT ====== Passing through a PCI device with at least one BAR in IO...

This source does not provide full text. Read it at seclists.org.