Skip to main content

Xen Hypervisor EUVDEUVD-2026-37888

| CVE-2026-42487 HIGH
Race Condition (CWE-362)
7.9
CVSS 3.1 · Vendor
Share

Severity by source

Vendor (CNA) PRIMARY
7.9 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
SUSE
7.8 HIGH
AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from Vendor (CNA).

CVSS VectorVendor

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

1
Analysis Generated
Jun 09, 2026 - 14:18 vuln.today

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

AnalysisAI

Unsynchronized traversal of HVM I/O port translation linked lists in the Xen hypervisor on x86 systems exposes a race condition exploitable by a compromised or malicious device model. The hypervisor manages I/O port translations via a linked list modified by the device model through XEN_DOMCTL_ioport_mapping; because traversal of that list during I/O port handling was never synchronized against concurrent modifications, a racing update can corrupt traversal state. The resulting hypervisor crash causes a Denial of Service of the entire host, with privilege escalation and information leakage explicitly acknowledged as non-ruled-out consequences - all without any active CISA KEV listing or public exploit identified at time of analysis.

Technical ContextAI

The Xen hypervisor's x86 HVM subsystem routes guest I/O port accesses through either direct emulation or translation tables managed by the guest's device model. The device model updates these translations at runtime via the XEN_DOMCTL_ioport_mapping hypercall, which manipulates an internal linked list. The vulnerability is a classic concurrent data structure access flaw: the hypervisor's I/O port dispatch path traverses this linked list without holding any lock or performing any synchronization against concurrent modification by the device model. This is consistent with CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) or CWE-416 (Use After Free) depending on whether the race produces a freed-node dereference. The flaw has been present since at least Xen 3.2; the advisory notes that even earlier versions were not audited, so the true origin is unknown. ARM architectures do not implement the affected HVM I/O port translation path and are confirmed not vulnerable.

Affected ProductsAI

All Xen versions from 3.2 onwards on x86 hardware are vulnerable; the advisory notes that versions earlier than 3.2 were not inspected, so the true lower bound is unconfirmed. Only x86 systems are affected - ARM is explicitly confirmed safe. The vulnerability is scoped to deployments running HVM guests whose device model operates in either a stub domain or in a de-privileged Dom0 process. Patches are available for Xen 4.17.x through 4.21.x via xsa491-4.21.patch (SHA256: 443674f42a092b953b6ba4d91cfa19bfbee0077dfcd5a39ae53368e40ed23aac) and for xen-unstable via xsa491.patch (SHA256: 23a90da1c71389083351846169fc565a671b44f5f4ba838b18fc0fa6d7582bf8). No formal CPE strings were supplied in the intelligence data. The Xen Project advisory is accessible via the oss-security list at https://seclists.org/oss-sec/2026/q2/857.

RemediationAI

Apply the XSA-491 patches distributed by the Xen Project: xsa491-4.21.patch targets Xen 4.17.x through 4.21.x stable branches, and xsa491.patch targets xen-unstable. Downstream distributions are advised to update to the tip of the relevant stable branch before applying, as patches are prepared against stable branch tips and may not apply cleanly to release tarballs. Patch availability is confirmed by the Xen Security Team with published SHA256 checksums; however, a specific released version number incorporating the fix has not been independently confirmed from the available data - treat this as 'upstream fix available via patch.' If patching is not immediately possible, the documented workaround is to run only PV (paravirtualized) or PVH guests, which eliminates the HVM I/O port translation path entirely and removes the attack surface; the trade-off is loss of HVM guest support, which may be operationally disruptive. Critically, the advisory explicitly warns that switching from a stub-domain or de-privileged device model to a fully privileged Dom0 device model does NOT mitigate the vulnerability - it only reclassifies the attacker as 'hostile management code' and should not be adopted as a compensating control. Advisory reference: https://seclists.org/oss-sec/2026/q2/857.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS Fixed
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS Fixed
SUSE Linux Enterprise Micro 5.5 Fixed
SUSE Linux Enterprise Server 15 SP5-LTSS Fixed
SUSE Linux Enterprise Server 15 SP6-LTSS Fixed

Share

EUVD-2026-37888 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy