# CVE-2025-58147: x86: Incorrect input sanitisation in Viridian hypercalls

> Out-of-bounds writes in Xen hypervisor Viridian hypercalls allow guest-to-host code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Oct 2025
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2025-58147, DEBIAN-CVE-2025-58147, GHSA-64c5-3xxf-ccjp, UBUNTU-CVE-2025-58147, openSUSE-SU-2025:15673-1

## What is CVE-2025-58147?

CVE-2025-58147 is a high-severity memory corruption vulnerability in Xen Xen, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]

Some Viridian hypercalls can specify a mask of vCPU IDs as an input, in
one of three formats.  Xen has boundary checking bugs with all three
formats, which can cause out-of-bounds reads and writes while processing
the inputs.

 * CVE-2025-58147.  Hypercalls using the HV_VP_SET Sparse format can
   cause vpmask_set() to write out of bounds when converting the bitmap
   to Xen's format.

 * CVE-2025-58148.  Hypercalls using any input format can cause
   send_ipi() to read d->vcpu[] out-of-bounds, and operate on a wild
   vCPU pointer.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-58147?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xen` | openSUSE:Tumbleweed | All versions | 4.20.1_06-1.1 |

Products: Xen Xen.

## How do I fix CVE-2025-58147?

Apply the vendor's patch.

## Is CVE-2025-58147 being exploited?

There is no known exploitation of CVE-2025-58147 in the wild and no public exploit code.

## Other vulnerabilities in Xen Xen

- [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0)
- [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58147 and fix it if it is affected.

What it is: CVE-2025-58147 is a high-severity memory corruption vulnerability in Xen Xen, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58147 in the wild and no public exploit code.

Affected product: Xen Xen. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58147/ (Markdown: https://insights.sbomify.com/CVE-2025-58147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58147
- OSV: https://osv.dev/vulnerability/CVE-2025-58147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58147/
Summaries are generated and may contain mistakes; the official description above is the record.