LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25596: An issue was discovered in Xen through 4.14.x.

An issue was discovered in Xen through 4.14.x. x86 PV guest kernels can experience denial of service via SYSENTER. The SYSENTER instruction leaves various state sanitization activities to software. One of Xen's sanitization paths injects a #GP fault, and incorrectly delivers it twice to the guest. This causes the guest kernel to observe a kernel-privilege #GP fault (typically fatal) rather than a user-privilege #GP fault (usually converted into SIGSEGV/etc.). Malicious or buggy userspace can crash the guest kernel, resulting in a VM Denial of Service. All versions of Xen from 3.2 onwards are vulnerable. Only x86 systems are vulnerable. ARM platforms are not vulnerable. Only x86 systems that support the SYSENTER instruction in 64bit mode are vulnerable. This is believed to be Intel, Centaur, and Shanghai CPUs. AMD and Hygon CPUs are not believed to be vulnerable. Only x86 PV guests can exploit the vulnerability. x86 PVH / HVM guests cannot exploit the vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Xen flaw lets malicious or faulty code inside an affected paravirtualized guest crash that guest’s kernel. The practical business impact is virtual machine denial of service, not documented host compromise. Exposure is narrow: x86 Xen PV guests on certain CPU families; ARM, AMD, Hygon, PVH, and HVM guests are described as not vulnerable. Highest exposure is infrastructure running Xen x86 PV guests on CPUs believed affected: Intel, Centaur, and Shanghai. Systems using ARM, AMD, Hygon, x86 PVH, or x86 HVM are described as not exploitable by this issue. Confirm against vendor advisories because package-level fixed versions are not provided in the source bundle. Treat this as a targeted availability risk for Xen virtualization estates, especially service providers or internal platforms relying on PV guests. It warrants normal urgent patch management where affected, but the sources do not support emergency treatment for environments without x86 PV guests or affected CPUs. Mitigation focus: Apply Xen or distribution security updates from the relevant vendor advisory.; Prioritize hosts running x86 PV guests on affected CPU families.; Where operationally supported, migrate exposed PV guests to PVH or HVM..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-25596 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.