CVE-2025-58147
BaseFortify
Publication date: 2025-10-31
Last updated on: 2025-11-04
Assigner: Xen Project
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xen | xen | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-58147 is a vulnerability in the Xen hypervisor related to Viridian hypercalls that accept a mask of virtual CPU (vCPU) IDs. Specifically, when using the HV_VP_SET Sparse format, a boundary checking bug in the vpmask_set() function can cause out-of-bounds writes while converting the bitmap to Xen's internal format. This means that the hypercall can write data outside the intended memory area, potentially corrupting memory or causing other unintended behavior. [1]
How can this vulnerability impact me? :
This vulnerability can be exploited by a malicious or buggy guest virtual machine (VM) running on an affected Xen hypervisor to cause Denial of Service (DoS) on the host system, leak information, or escalate privileges. Essentially, it can allow an attacker controlling a guest VM to disrupt the host or gain unauthorized access or information. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves identifying if your Xen hypervisor is running vulnerable versions (4.15 and newer) with Viridian hypercalls enabled on x86 HVM guests. Since the vulnerability arises from malformed hypercalls specifying vCPU ID masks, monitoring or logging hypercall activity related to Viridian features may help. However, no specific detection commands or tools are provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling Viridian on x86 HVM guests, as disabling Viridian prevents exploitation. Additionally, applying the patches provided in Xen Security Advisory XSA-475 for your Xen stable branch (4.17.x through 4.20.x) is recommended. Users should update to the tip of the stable branch before applying patches. Note that some Viridian configuration options do not block the vulnerable hypercalls, so disabling Viridian entirely is advised until patches are applied. [1]