# CVE-2025-58149: Incorrect removal of permissions on PCI device unplug

> Attackers can retain access to 64-bit memory BARs after PCI device unplug, allowing unauthorized memory mapping and potential 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-58149, DEBIAN-CVE-2025-58149, GHSA-38qg-7h9q-7h29, SUSE-SU-2025:4419-1, SUSE-SU-2025:4490-1, UBUNTU-CVE-2025-58149, openSUSE-SU-2025:15719-1

## What is CVE-2025-58149?

CVE-2025-58149 is a high-severity missing authorization 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

When passing through PCI devices, the detach logic in libxl won't remove
access permissions to any 64bit memory BARs the device might have.  As a
result a domain can still have access any 64bit memory BAR when such
device is no longer assigned to the domain.

For PV domains the permission leak allows the domain itself to map the memory
in the page-tables.  For HVM it would require a compromised device model or
stubdomain to map the leaked memory into the HVM domain p2m.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xen` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.17.6_02-150500.3.56.1 |
| `xen` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.20.2_02-150700.3.19.1 |
| `xen` | SUSE:Linux Enterprise Module for Server Applications 15 SP7 | All versions | 4.20.2_02-150700.3.19.1 |
| `xen` | openSUSE:Tumbleweed | All versions | 4.20.1_08-1.1 |

Products: Xen Xen.

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

Apply the vendor's patch.

## Is CVE-2025-58149 being exploited?

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

What it is: CVE-2025-58149 is a high-severity missing authorization 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-58149 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-58149/ (Markdown: https://insights.sbomify.com/CVE-2025-58149/index.md)
```

## Sources

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

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