Skip to main content

Xen CVE-2026-62433

| EUVDEUVD-2026-49786 HIGH
Improper Initialization (CWE-665)
2026-07-28 security@xen.org GHSA-cfmp-p477-x9qv
7.3
CVSS 3.1 · Vendor: xen
Share

Severity by source

Vendor (xen) PRIMARY
7.3 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI
3.8 LOW

DM_OP is a local privileged hypercall from a device model (AV:L/PR:L); a device model reading hypervisor memory crosses a trust boundary (S:C); impact is limited stack-memory disclosure only (C:L, I:N/A:N).

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
SUSE
5.9 MEDIUM
AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Primary rating from Vendor (xen).

CVSS VectorVendor: xen

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

3
Analysis Generated
Jul 28, 2026 - 16:46 vuln.today
CVE Published
Jul 28, 2026 - 13:19 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 28, 2026 - 13:19 cve.org
HIGH 7.3

DescriptionCVE.org

Parts of the DM_OP handling code assumes the caller has provided the required number of buffers for the given operation without any checking being done. As a result, certain operations might access stack rubble as structures are possibly uninitialized.

AnalysisAI

Information disclosure in the Xen hypervisor's DM_OP (device model operation) hypercall handling allows a device model caller to leak uninitialized hypervisor stack memory because certain operations do not verify that the required number of buffers was supplied before reading them. Affected Xen builds process DM_OP requests using structures that may remain uninitialized ('stack rubble'), disclosing low-value memory contents (CWE-665) with limited integrity and availability side effects. No public exploit has been identified at time of analysis; SSVC records exploitation status as none, EPSS is low (0.26%, 18th percentile), and it is not on CISA KEV.

Technical ContextAI

Xen is a bare-metal (type-1) hypervisor widely used for server and cloud virtualization. DM_OP is the hypercall interface through which a device model (the emulator component, typically QEMU running in a control or stub domain) requests emulation-related services from the hypervisor for HVM/PVH guests. The interface passes a set of caller-provided buffers, and the hypervisor is supposed to validate that the count and sizes match the requested operation. The root cause maps to CWE-665 (Improper Initialization): parts of the DM_OP dispatch path trust the caller to supply the correct number of buffers and skip the check, so operations dereference or copy from structures that were never populated, exposing residual hypervisor stack data. The vendor (Xen Project) tracks this as XSA-506.

Affected ProductsAI

The Xen hypervisor is affected wherever the DM_OP handling code lacks buffer-count validation; the Xen Project advisory XSA-506 (https://xenbits.xenproject.org/xsa/advisory-506.html and mirror http://xenbits.xen.org/xsa/advisory-506.html) is the authoritative source for the exact affected version ranges and patched releases, which are not enumerated in the provided intelligence (no CPE strings were supplied). This is also tracked as ENISA EUVD EUVD-2026-49786 and VulDB entry https://vuldb.com/vuln/383868. Deployments running HVM/PVH guests with a device model (QEMU) are in scope; consult XSA-506 to map the fix against your specific Xen version.

RemediationAI

Apply the patches published in Xen Project advisory XSA-506 (https://xenbits.xenproject.org/xsa/advisory-506.html), which add the missing buffer-count checks in the DM_OP dispatch path; the advisory carries the per-branch patch set and any tagged releases - Patch available per vendor advisory (exact fix version not enumerated in the provided data, confirm against XSA-506 for your Xen branch). Rebuild/redeploy the hypervisor and restart the affected hosts (typically requiring guest migration or a maintenance window) to load the corrected hypervisor. Where immediate patching is not possible, reduce exposure by ensuring device models run deprivileged in stub domains (dm_restrict) so a compromised or buggy device model cannot leverage the leak beyond its own domain, and limit which domains are permitted to act as device models; note these controls reduce blast radius but do not close the underlying missing-check flaw. See also the oss-security disclosure at https://seclists.org/oss-sec/2026/q3/310.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS Fixed
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS Fixed
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.3 Fixed

Share

CVE-2026-62433 vulnerability details – vuln.today

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