Quick answers
- Is CVE-2026-62427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62427 being exploited in the wild.
- How severe is CVE-2026-62427?
- Informational severity, with a CVSS score of 0, published 28 July 2026.
- Which products and versions are affected?
- Xen Project Xen 4.0 and later.
- Is there a fix for CVE-2026-62427?
- A patch was published on 2026-07-28: Patches released for Xen 4.17 through 4.21 (unstable) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62427 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-62427?
- Check whether you run Xen Project Xen at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the Xen hypervisor's handling of platform operations (platform-op). The system uses system-wide locks to manage operations that cannot be executed in parallel; however, these locks lack fairness in their acquisition logic. Furthermore, when XSM/Flask is enabled, the lock is acquired before permission checks are performed. This allows a less privileged domain or entity to repeatedly acquire or contest the lock, effectively stalling more privileged entities (such as the control domain). This can lead to a host-wide Denial of Service (DoS). The issue is resolved by applying patches provided in XSA-499.
Affected products
- Xen Project Xen 4.0 and later
Timeline
- 2026-07-28: disclosed: Public release of XSA-499
- 2026-07-28: patched: Patches released for Xen 4.17 through 4.21 (unstable)