Skip to content
Fencer Intel
medium 4.7

CVE-2020-25604 json

An issue was discovered in Xen through 4.14.x.

published 6y ago modified 4mo ago also EUVD-2020-18283

cvss
4.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

An issue was discovered in Xen through 4.14.x. There is a race condition when migrating timers between x86 HVM vCPUs. When migrating timers of x86 HVM guests between its vCPUs, the locking model used allows for a second vCPU of the same guest (also operating on the timers) to release a lock that it didn't acquire. The most likely effect of the issue is a hang or crash of the hypervisor, i.e., a Denial of Service (DoS). All versions of Xen are affected. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only x86 HVM guests can leverage the vulnerability. x86 PV and PVH cannot leverage the vulnerability. Only guests with more than one vCPU can exploit the vulnerability.

Patch / fix

  • xen Debian 14, Debian 13, Debian 12 4.14.0+80-gd101b417b7-1

debian advisories DEBIAN-CVE-2020-25604

  • xen Ubuntu 20.04 LTS 4.11.3+24-g14b62ab3e5-1ubuntu2.3

ubuntu advisories UBUNTU-CVE-2020-25604

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • xen SLES for SAP 12 SP2, SLES 12 SP2-LTSS, SLES 12 SP2-BCL +1 more 4.7.6_10-43.67.1
  • xen SLE Module for Server Applications 15 SP2, SLE Module for Basesystem 15 SP2 4.13.1_08-3.10.1
  • xen SLE Module for Server Applications 15 SP1, SLE Module for Basesystem 15 SP1 4.12.3_08-3.28.1
  • xen SLES for SAP 15, SLE High Performance Computing 15-LTSS, SLE High Performance Computing 15-ESPOS 4.10.4_16-3.41.1
  • xen SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.12.3_08-3.24.1
  • xen SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +4 more 4.9.4_12-3.74.1
  • xen SLES for SAP 12 SP4, SLES 12 SP4-LTSS, OpenStack Cloud Crowbar 9 +1 more 4.11.4_08-2.36.1
  • xen SLES 11 SP4-LTSS 4.4.4_44-61.55.1

suse advisories SUSE-SU-2020:14521-1SUSE-SU-2020:2822-1SUSE-SU-2020:2791-1SUSE-SU-2020:2790-1SUSE-SU-2020:2789-1SUSE-SU-2020:2788-1

  • xen openSUSE Tumbleweed 4.15.1_01-1.2
  • xen openSUSE Leap 15.2 4.13.1_08-lp152.2.9.1

opensuse advisories openSUSE-SU-2024:11520-1openSUSE-SU-2020:1608-1

  • xen Alpine 3.10 4.12.3-r4
  • xen Alpine 3.12, Alpine 3.11 4.13.1-r4
  • xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 4.14.0-r1
  • xen Alpine 3.9 4.11.4-r2

alpine advisories ALPINE-CVE-2020-25604

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-25604 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-25604 updated cvss 5.6

xen: race when migrating timers between x86 HVM vCPU-s (XSA-336)

  • Red Hat Enterprise Linux 5 kernel-xen
    affected: workaround, no fix planned “There is no known mitigation for this flaw apart from applying the patch.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.