dbcve.org
XenOperating system

CVE-2025-58144

HIGH · 7.5 CVSS v3.1 Published 2025-09-11
Fix available
A fix is available. Upgrade to 4.17.0 or later.
See remediation →
84/100
Remediation priority · High
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 two issues related to the mapping of pages belonging to other domains: For one, an assertion is wrong there, where the case actually needs handling. A NULL pointer de-reference could result on a release build. This is CVE-2025-58144. And then the P2M lock isn't held until a page reference was actually obtained (or the attempt to do so has failed). Otherwise the page can not only change type, but even ownership in between, thus allowing domain boundaries to be violated. This is CVE-2025-58145.

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 · moderate confidence

Xen hypervisor contains a vulnerability in page mapping code for pages belonging to other domains where an incorrect assertion fails to handle a valid case, leading to NULL pointer dereference on release builds. Combined with the related P2M lock timing issue (CVE-2025-58145) where page references aren't properly secured, this allows domain boundaries to be violated.

MitigationApply Xen security patches addressing CVE-2025-58144 and CVE-2025-58145; update hypervisor to patched version and verify domain isolation remains intact.

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.12.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Xen hypervisor version
    Run 'xl info' or 'xm info' to display hypervisor information, or check '/usr/lib/xen-*/bin/xen' version. Also 'cat /proc/xen/versions' may show version details.
    Affected if Installed version is >= 4.12.0 and < 4.17.0
  2. Confirm system is running Xen hypervisor
    Check for Xen kernel or hypervisor presence: 'uname -a' shows 'xen' in kernel name, or 'xl list' / 'xm list' returns domain list, or check /proc/xen/ exists.
    Affected if System is running Xen as the hypervisor (not bare metal or other hypervisor)
  3. Verify active domains exist
    Run 'xl list' or 'xm list' to list running domains. The vulnerability affects page mapping between domains, requiring multiple domains to be present.
    Affected if Multiple domains (dom0 plus at least one domU) are running
  4. Check for domain isolation configuration
    Examine Xen configuration in /etc/xen/ or via 'xl list -l' for each domain. Verify paravirtualization (PV) or hardware virtualization (HVM) configuration as the vulnerability relates to P2M (Physical to Machine) page table handling.
    Affected if Domains are configured with memory mapping that could access other domain pages

Environment is affected if running Xen hypervisor version 4.12.0 through 4.16.x with multiple active domains, as the vulnerability allows boundary violations between domains through flawed page mapping code.

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 Xen security patches addressing CVE-2025-58144 and CVE-2025-58145; update hypervisor to patched version and verify domain isolation remains intact.

Recommended fix High confidence

Xen 4.17.0 or later

  1. Upgrade Xen hypervisor to version 4.17.0 or later to address the NULL pointer dereference vulnerability (CVE-2025-58144)
  2. After upgrading, verify the hypervisor boots correctly and all VMs start as expected
  3. Consult Xen 4.17.0 release notes for any specific configuration or compatibility changes that may be required
Caveat Review Xen 4.17.0 release notes for any guest compatibility or configuration changes before upgrading production systems

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

Fix this in Xen Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58144 — 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-58144 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