CVE-2020-25603: An issue was discovered in Xen through 4.14.x.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: xen (Alpine:v3.10) 4.12.3-r4; xen (Alpine:v3.11) 4.13.1-r4; xen (Alpine:v3.13) 4.14.0-r1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to xen (Alpine:v3.10) 4.12.3-r4; xen (Alpine:v3.11) 4.13.1-r4; xen (Alpine:v3.13) 4.14.0-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory barrier (e.g., smp_*mb()) to prevent both the compiler and CPU from re-ordering access. A malicious guest may be able to cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded. Systems running all versions of Xen are affected. Whether a system is vulnerable will depend on the CPU and compiler used to build Xen. For all systems, the presence and the scope of the vulnerability depend on the precise re-ordering performed by the compiler used to build Xen. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code generation options). GCC documentation clearly suggests that re-ordering is possible. Arm systems will also be vulnerable if the CPU is able to re-order memory access. Please consult your CPU vendor. x86 systems are only vulnerable if a compiler performs re-ordering.
- Published
- Sep 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-670
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xen | xen | cpe:2.3:o:xen:xen |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- fedoraproject fedora31
- fedoraproject fedora32
- fedoraproject fedora33
- opensuse leap15.2
- xen xenup to 4.14.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | xen | before 4.12.3-r4 | 4.12.3-r4 |
| Alpine:v3.11 | xen | before 4.13.1-r4 | 4.13.1-r4 |
| Alpine:v3.13 | xen | before 4.14.0-r1 | 4.14.0-r1 |
| Alpine:v3.9 | xen | before 4.11.4-r2 | 4.11.4-r2 |
| Debian:10 | xen | before 4.11.4+37-g3263f257ca-1 | 4.11.4+37-g3263f257ca-1 |
| Debian:12 | xen | before 4.14.0+80-gd101b417b7-1 | 4.14.0+80-gd101b417b7-1 |
| openSUSE:Leap 15.2 | xen | before 4.13.1_08-lp152.2.9.1 | 4.13.1_08-lp152.2.9.1 |
| SUSE:HPE Helion OpenStack 8 | xen | before 4.9.4_12-3.74.1 | 4.9.4_12-3.74.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | xen | before 4.10.4_16-3.41.1 | 4.10.4_16-3.41.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | xen | before 4.12.3_08-3.28.1 | 4.12.3_08-3.28.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | xen | before 4.13.1_08-3.10.1 | 4.13.1_08-3.10.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | xen | before 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.3_08-3.24.1 | 4.12.3_08-3.24.1 |
| SUSE:OpenStack Cloud 7 | xen | before 4.7.6_10-43.67.1 | 4.7.6_10-43.67.1 |
| SUSE:OpenStack Cloud 9 | xen | before 4.11.4_08-2.36.1 | 4.11.4_08-2.36.1 |
Same product
xen: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…41Plan
- CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…41Plan
- CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-25601Sep 23, 2020 · An issue was discovered in Xen through 4.14.x.22Monitor
- ← EarlierCVE-2020-25602Sep 23, 2020 · An issue was discovered in Xen through 4.14.x.24Monitor
- Later →CVE-2020-25604Sep 23, 2020 · An issue was discovered in Xen through 4.14.x.18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:xen | 4.12.3-r4 · Alpine:v3.10 | Package registry (OSV) |
| debian:xen | 4.14.0+80-gd101b417b7-1 · Debian:12 | Package registry (OSV) |
| opensuse:xen | 4.13.1_08-lp152.2.9.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:xen | 4.4.4_44-61.55.1 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-781 · Sep 24, 2020(Xen Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-670 · Always-Incorrect Control Flow ImplementationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4JRXMKEMQRQYWYEPHVBIWUEAVQ3LU4FN/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DA633Y3G5KX7MKRN4PFEGM3IVTJMBEOM/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RJZERRBJN6E6STDCHT4JHP4MI6TKBCJE/
- security.gentoo.org/glsa/202011-06
- www.debian.org/security/2020/dsa-4769
- xenbits.xen.org/xsa/advisory-340.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.