CVE-2026-42489 | domctl lock open to abuse

[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] To create and manage guests, domctl operations are used by the control domain, a possible Xenstore domain, or by a domain controlling a particular guest. Some of these operations may not be executed in parallel, so a system-wide lock is used. The way that lock is acquired is, however, not providing any fairness. This is CVE-2026-42489. Furthermore, with XSM/Flask in use, the lock acquire will, for some operations, occur ahead of any permission checking. This is CVE-2026-42490.

Published: 2026-06-18 Last update: 2026-06-22 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-42489 is rated Low Risk (32.6/100): CVSS Medium severity. Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-42489

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

EPSS has not published a score for this CVE yet—common while NVD analysis or FIRST scoring is still pending. Monitor daily updates and reassess once scores appear.

Common vulnerability scoring system (CVSS) metrics for CVE-2026-42489

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 4.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-42489

GitHub Security Advisory for CVE-2026-42489

GHSA-vw8q-74w5-57vq · Severity: medium — [This CNA information record relates to multiple CVEs; the text explains which aspects...

OS Trackers for CVE-2026-42489

vendor priority summary link
debian end-of-life CVE-2026-42489 end-of-life priority: Debian including 1 source packages (xen), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2026-42489
suse medium CVE-2026-42489 severity moderate: SUSE including 18 source package names (xen-4.17.6_12-150500.3.73.1, xen-4.18.5_18-150600.3.50.1, …), 43 product×package rows across 9 product lines (SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (9 product lines)): Fixed 43. https://www.suse.com/security/cve/CVE-2026-42489/
ubuntu medium CVE-2026-42489 medium priority: Ubuntu including 1 source packages (xen), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, resolute, upstream, xenial): needs-triage 8. https://ubuntu.com/security/CVE-2026-42489

Affected software / configurations for CVE-2026-42489

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-42489

cvelogic Threat Intelligence