Cyber Resilience

CVE-2025-58149

Xen ≥ 4.0.0

Published
31 October 2025
Modified
14 January 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0040 34th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-58149 is a high-severity Operation on a Resource after Expiration or Release (CWE-672) vulnerability in Xen Xen. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-34326Same product: Xen Xen
CVE-2023-46837Same product: Xen Xen
CVE-2023-34321Same product: Xen Xen
CVE-2025-58147Same product: Xen Xen
CVE-2025-58150Same product: Xen Xen
CVE-2023-46835Same product: Xen Xen
CVE-2023-34325Same product: Xen Xen
CVE-2025-58148Same product: Xen Xen
CVE-2026-23558Same product: Xen Xen
CVE-2025-58145Same product: Xen Xen

Affected Assets

xen
xen
≥ 4.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement applies current authorizations to every request, directly blocking operations once a resource has been revoked or released.

Authenticator management mandates revocation and replacement procedures that render expired credentials unusable.

Account lifecycle management includes explicit revocation and disabling steps that stop subsequent operations on released accounts or identifiers.

Identifier management requires deallocation and reuse controls that prevent continued use of released identifiers.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Enforcing managed authorizations and revocations directly prevents post-release operations on credentials or entitlements.

PR.PS-06 mostly match
prevents

Secure development practices eliminate the root coding flaw that permits use-after-release.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect use-after-release but does not prevent it at runtime.

degrades

Enforces timely deletion of resources so they cannot be used after release.

prevents

Secure-coding rules require checks that prevent operations on freed or expired objects.

prevents

Change-management processes can introduce or remove resource-lifetime controls.

References