CVE-2025-58145
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-11

Last updated on: 2025-11-04

Assigner: Xen Project

Description
[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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-11
Last Modified
2025-11-04
Generated
2026-06-16
AI Q&A
2025-09-11
EPSS Evaluated
2026-06-15
NVD
CVE-2025-58145
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
xen xen From 4.12.0 (inc) to 4.17.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-58145 is a vulnerability in the Xen hypervisor where the P2M lock is not held until a page reference is obtained or the attempt fails. This flaw allows the page type or ownership to change in between, which can lead to violations of domain boundaries. Essentially, this means that memory pages belonging to one domain could be improperly accessed or manipulated by another domain, breaking isolation guarantees. [1]

Impact Analysis

This vulnerability can allow domain boundary violations, meaning that one domain could potentially access or interfere with memory pages of another domain. This breaks the isolation between virtual machines or domains, potentially leading to unauthorized access or manipulation of data. It could also lead to instability or security breaches in systems relying on Xen for virtualization. [1]

Mitigation Strategies

The immediate step to mitigate this vulnerability is to apply the patches provided for the affected Xen stable branches (4.17.x through 4.19.x). No other known mitigations exist. It is recommended to update to the tip of the stable branch before applying these patches to fix the assertion handling and locking issues that cause the vulnerability. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-58145. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart