CVE-2020-25598
published 2020-09-23CVE-2020-25598: An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.42%
33.7th percentile
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock. A buggy or malicious HVM stubdomain can cause an RCU reference to be leaked. This causes subsequent administration operations, (e.g., CPU offline) to livelock, resulting in a host Denial of Service. The buggy codepath has been present since Xen 4.12. Xen 4.14 and later are vulnerable to the DoS. The side effects are believed to be benign on Xen 4.12 and 4.13, but patches are provided nevertheless. The vulnerability can generally only be exploited by x86 HVM VMs, as these are generally the only type of VM that have a Qemu stubdomain. x86 PV and PVH domains, as well as ARM VMs, typically don't use a stubdomain. Only VMs using HVM stubdomains can exploit the vulnerability. VMs using PV stubdomains, or with emulators running in dom0, cannot exploit the vulnerability.
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | xen | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| opensuse | leap | — | — |
| xen | xen | >= 0 < 4.12.3-r4 | 4.12.3-r4 |
| xen | xen | >= 0 < 4.13.1-r4 | 4.13.1-r4 |
| xen | xen | >= 0 < 4.13.1-r4 | 4.13.1-r4 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | >= 0 < 4.14.0-r1 | 4.14.0-r1 |
| xen | xen | 4.12.0 – 4.14.0 | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:N/I:N/A:P
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
vendor_redhat·2020-09-22·CVSS 5.5
CVE-2020-25598 [MEDIUM] CWE-667 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock. A buggy or malicious HVM stubdomain can cause an RCU reference to be leaked. This causes subsequent administration operations, (e.g., CPU offline) to livelock, resulting in a host Denial of Service. The buggy codepath has been present since Xen 4.12. Xen 4.14 and later are vulnerable to the DoS. The side effects are believed to be benign on Xen 4.12 and 4.13, but patches are provided neverth
Debian
CVE-2020-25598: xen - An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_a...
vendor_debian·2020·CVSS 5.5
CVE-2020-25598 [MEDIUM] CVE-2020-25598: xen - An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_a...
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock. A buggy or malicious HVM stubdomain can cause an RCU reference to be leaked. This causes subsequent administration operations, (e.g., CPU offline) to livelock, resulting in a host Denial of Service. The buggy codepath has been present since Xen 4.12. Xen 4.14 and later are vulnerable to the DoS. The side effects are believed to be benign on Xen 4.12 and 4.13, but patches are provided nevertheless. The vulnerability can generally only be exploited by x86 HVM V
GHSA
GHSA-6vvr-9x9v-68j4: An issue was discovered in Xen 4
ghsa_unreviewed·2022-05-24
CVE-2020-25598 [MEDIUM] CWE-670 GHSA-6vvr-9x9v-68j4: An issue was discovered in Xen 4
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock. A buggy or malicious HVM stubdomain can cause an RCU reference to be leaked. This causes subsequent administration operations, (e.g., CPU offline) to livelock, resulting in a host Denial of Service. The buggy codepath has been present since Xen 4.12. Xen 4.14 and later are vulnerable to the DoS. The side effects are believed to be benign on Xen 4.12 and 4.13, but patches are provided nevertheless. The vulnerability can generally only be exploited by x86 HVM V
OSV
CVE-2020-25598: An issue was discovered in Xen 4
osv·2020-09-23·CVSS 5.5
CVE-2020-25598 [MEDIUM] CVE-2020-25598: An issue was discovered in Xen 4
An issue was discovered in Xen 4.14.x. There is a missing unlock in the XENMEM_acquire_resource error path. The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock. A buggy or malicious HVM stubdomain can cause an RCU reference to be leaked. This causes subsequent administration operations, (e.g., CPU offline) to livelock, resulting in a host Denial of Service. The buggy codepath has been present since Xen 4.12. Xen 4.14 and later are vulnerable to the DoS. The side effects are believed to be benign on Xen 4.12 and 4.13, but patches are provided nevertheless. The vulnerability can generally only be exploited by x86 HVM V
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334) [fedora-all]
bugzilla·2020-09-22·CVSS 5.5
CVE-2020-25598 [MEDIUM] CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334) [fedora-all]
CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334) [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple
Bugzilla
CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
bugzilla·2020-09-09·CVSS 5.5
CVE-2020-25598 [MEDIUM] CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
CVE-2020-25598 xen: missing unlock in XENMEM_acquire_resource error path (XSA-334)
The RCU (Read, Copy, Update) mechanism is a synchronisation primitive. A buggy error path in the XENMEM_acquire_resource exits without releasing an RCU reference, which is conceptually similar to forgetting to unlock a spinlock.
Discussion:
Acknowledgments:
Name: the Xen project
---
Statement:
This issue can generally only be exploited by x86 HVM guests, as these are the only type of VM which have a QEMU stubdomain. x86 PV and PVH domains, as well as ARM guests typically don't use a stubdomain. Additionally, VMs using PV stubdomains or with emulators running in dom0 cannot exploit the vulnerability.
Xen 4.14 and later versions are vulnerable to this flaw. Red Hat Enterprise Linux 5 is not affected, a
http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00008.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4JRXMKEMQRQYWYEPHVBIWUEAVQ3LU4FN/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DA633Y3G5KX7MKRN4PFEGM3IVTJMBEOM/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RJZERRBJN6E6STDCHT4JHP4MI6TKBCJE/https://security.gentoo.org/glsa/202011-06https://xenbits.xen.org/xsa/advisory-334.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-10/msg00008.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4JRXMKEMQRQYWYEPHVBIWUEAVQ3LU4FN/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DA633Y3G5KX7MKRN4PFEGM3IVTJMBEOM/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RJZERRBJN6E6STDCHT4JHP4MI6TKBCJE/https://security.gentoo.org/glsa/202011-06https://xenbits.xen.org/xsa/advisory-334.html
2020-09-23
Published