dbcve.org
XenOperating system

CVE-2025-58145

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

In Xen's P2M (Physical to Machine) mapping code, the lock protecting page table entries is released before a page reference is actually obtained. This race condition allows pages to change type or ownership between lock release and reference capture, enabling domain boundary violations where one VM can potentially access another VM's memory.

MitigationApply the Xen security patch for CVE-2025-58145 to ensure the P2M lock is held until page references are actually obtained, preventing domain isolation bypass.

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. Verify Xen hypervisor is installed
    Check for Xen installation by examining /proc/xen/version, running 'xl version' or 'xm version', or checking if the xen kernel module is loaded with 'lsmod | grep xen'
    Affected if The system is not running Xen hypervisor - this CVE does not apply to other hypervisors or bare metal
  2. Identify the running Xen version
    Execute 'xl version' or 'xm version' to obtain the Xen hypervisor version number. Alternatively, check 'dmesg | grep -i xen' for version information logged at boot.
    Affected if Unable to determine the Xen version - cannot assess CVE applicability
  3. Compare installed version against affected range
    Compare the identified Xen version to the affected range: >= 4.12.0 and < 4.17.0. Note that versions 4.12.0 through 4.16.x inclusive are affected.
    Affected if The installed Xen version falls within the range >= 4.12.0 and < 4.17.0 (versions 4.12.0 through 4.16.x)
  4. Confirm P2M functionality is in use
    This is implicit in any Xen installation - the P2M (Physical to Machine) mapping code is core to how Xen virtualizes memory for all guests. No additional check needed.
    Affected if The environment uses Xen for virtualization (P2M code is always active)

The environment is affected if the system runs Xen hypervisor version 4.12.0 through 4.16.x, as the race condition in the P2M lock exists in these versions.

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-58145 to ensure the P2M lock is held until page references are actually obtained, preventing domain isolation bypass.

Recommended fix High confidence

Xen 4.17.0 or later stable release

  1. Identify current Xen version using 'xl version' or 'xm version' command
  2. Schedule a maintenance window for the hypervisor update
  3. Upgrade Xen to version 4.17.0 or later stable release using your distribution's package manager or from xenbits.xenproject.org
  4. Reboot the host(s) to load the updated hypervisor
  5. Verify the new version is running with 'xl version' and confirm it shows 4.17.0 or higher
Caveat Major Xen version upgrades may introduce hypervisor API or toolstack changes; review release notes for compatibility with your dom0 kernel and guest configurations before upgrading

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

Fix this in Xen Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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