dbcve.org
XenOperating system

CVE-2025-58142

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-11
Fix available
A fix is available. Upgrade to 4.17.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are multiple issues related to the handling and accessing of guest memory pages in the viridian code: 1. A NULL pointer dereference in the updating of the reference TSC area. This is CVE-2025-27466. 2. A NULL pointer dereference by assuming the SIM page is mapped when a synthetic timer message has to be delivered. This is CVE-2025-58142. 3. A race in the mapping of the reference TSC page, where a guest can get Xen to free a page while still present in the guest physical to machine (p2m) page tables. This is CVE-2025-58143.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A NULL pointer dereference vulnerability in Xen's viridian (Hyper-V compatibility layer) where the code assumes the SIM (synthetic interrupt message) page is mapped when delivering a synthetic timer message, but the page may not actually be mapped, leading to crash or potential code execution.

MitigationApply the Xen security patch for CVE-2025-58142. As a temporary workaround, consider disabling viridian (Hyper-V compatibility features) for affected virtual machines if operationally feasible, though this may impact Hyper-V guest functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XenOperating system
Affected:>= 4.13.0, < 4.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Xen hypervisor version
    Run 'xl version' or 'xm version' or check /etc/xen/version file
    Affected if Version is >= 4.13.0 and < 4.17.0
  2. List VMs with viridian feature enabled
    Run 'xl list -v' or 'xe vm-list params=name,platform' to check if any VM has platform='viridian=true' or similar Hyper-V compatibility flag set
    Affected if Any guest VM has viridian (Hyper-V compatibility) feature enabled in its configuration
  3. Verify SIM page mapping configuration
    Inspect Xen configuration files in /etc/xen or check VM configuration via 'xl cfggrep viridian' or 'xl vm-list' for platform settings
    Affected if VM platform settings include viridian feature flags without corresponding SIM page initialization

A system is affected if running Xen version 4.13.0 through 4.16.x AND has any guest VM configured with viridian (Hyper-V compatibility) features enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.17.0 or later
Fixed in 4.17.0
Interim mitigation

Apply the Xen security patch for CVE-2025-58142. As a temporary workaround, consider disabling viridian (Hyper-V compatibility features) for affected virtual machines if operationally feasible, though this may impact Hyper-V guest functionality.

Recommended fix High confidence

Xen 4.17.0

  1. 1. Schedule a maintenance window for the Xen hypervisor hosts.
  2. 2. Back up all VM configurations and critical data.
  3. 3. Upgrade Xen to version 4.17.0 or later.
  4. 4. After upgrade, verify that the viridian (Hyper-V compatibility) subsystem is functioning correctly.
  5. 5. Test VM operations including start, stop, and live migration to confirm stability.
  6. 6. Monitor for any related errors in the Xen logs (xl dmesg).
Caveat Review Xen 4.17.0 release notes for any guest or toolstack changes that may affect your environment before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xen Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58142 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data