ZeroHour
oss-securitypublished ()ingested
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 511 v3 (CVE-2026-79603) - Unconditionally do TLB flushing ahead of page scrubbing

mediumVulnerabilityimportance 35CVE-2026-79603
AI summary · glm-5.3-flash

Xen Project released XSA-511 (CVE-2026-79603) fixing missing TLB flushes before page scrubbing that can leak x86 PV guest data.

Xen Security Advisory 511 v3 publicly discloses CVE-2026-79603, a TLB handling flaw in the Xen hypervisor on x86. x86 PV guests can free memory pages while a stale TLB entry still points to them, and Xen only flushes the TLB when the page is reused, potentially exposing stale data ahead of scrubbing. The advisory changes Xen to unconditionally flush the TLB ahead of page scrubbing. The issue was published in version 3 of the advisory.

  • CVE-2026-79603 assigned to the TLB flush/scrubbing flaw
  • Affects x86 paravirtual (PV) guests releasing pages with stale TLB entries
  • Fix makes TLB flushing unconditional before page scrubbing
  • Published as public Xen Security Advisory XSA-511 v3
ProductsXen
OrganizationsXen Project

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-79603
Stale TLB Entry Flaw in Xen Hypervisor Lets x86 PV Guests Modify Scrubbed Pages

This is a memory-management flaw in the Xen hypervisor on x86 systems: a paravirtualized (PV) guest can free a memory page while a stale TLB (translation lookaside buffer) entry pointing to that page still exists, and Xen only issues a TLB flush, if needed, when the page is later re-used. Because the freed page can be scrubbed (zeroed) ahead of that deferred TLB flush, a window exists in which the guest can write to a page that has already been scrubbed, potentially corrupting or tainting memory Xen believes is clean. The practical impact, per the CVSS 3.1 score of 4.3 (medium, confidentiality impact only), is limited information exposure rather than privilege escalation or denial of service. Only operators of Xen hypervisors on x86 hardware that run PV guests are affected. Exploitation status is calm: there is no public proof-of-concept, the flaw is not in CISA's KEV catalog, and EPSS puts 30-day exploitation probability at just 0.2% (14th percentile).

Do: Upgrade Xen to a patched release per the version table in Xen Security Advisory 511 v3, which fixes the issue by unconditionally performing TLB flushing ahead of page scrubbing. Prioritize hosts running untrusted or multi-tenant PV guests, and consult the advisory for any interim workarounds if patching must be deferred. Administrators can also reduce exposure by migrating workloads from PV to HVM/PVH guest modes, which are not affected by this x86 PV-specific flaw.

4.3<1%
  • Xen Project Xen hypervisor (x86, with paravirtualized/PV guests) Affected version ranges are not specified in the available data; see Xen Security Advisory 511 v3 for the exact affected/patched version table
large≈ tens of thousands of Xen hosts (Xen remains the hypervisor behind many cloud and VPS providers, though only x86 hosts actually running PV guests are affected)
Full article

Posted by Xen . org security team on Sep 08 Xen Security Advisory CVE-2026-79603 / XSA-511 version 3 Unconditionally do TLB flushing ahead of page scrubbing UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= x86 PV guests can free memory pages while still keeping a stale TLB entry pointing to them. A TLB flush is only issued by Xen (if needed) when the page is re-used. Since it's...

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