# CVE-2025-58145: Arm issues with page refcounting

> A race condition in Xen allows attackers to violate domain boundaries, potentially leading to privilege escalation or unauthorized data access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2025
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2025-58145, DEBIAN-CVE-2025-58145, GHSA-j9v5-p5pj-rmp7, UBUNTU-CVE-2025-58145

## What is CVE-2025-58145?

CVE-2025-58145 is a high-severity vulnerability in Xen Xen, published on 11 Sep 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.]

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Xen Xen.

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

Apply the vendor's patch.

## Is CVE-2025-58145 being exploited?

There is no known exploitation of CVE-2025-58145 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-58145 and fix it if it is affected.

What it is: CVE-2025-58145 is a high-severity vulnerability in Xen Xen, published on 11 Sep 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-58145 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-58145/ (Markdown: https://insights.sbomify.com/CVE-2025-58145/index.md)
```

## Sources

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

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