CVE-2018-12891

Description

An issue was discovered in Xen through 4.10.x. Certain PV MMU operations may take a long time to process. For that reason Xen explicitly checks for the need to preempt the current vCPU at certain points. A few rarely taken code paths did bypass such checks. By suitably enforcing the conditions through its own page table contents, a malicious guest may cause such bypasses to be used for an unbounded number of iterations. A malicious or buggy PV guest may cause a Denial of Service (DoS) affecting the entire host. Specifically, it may prevent use of a physical CPU for an indeterminate period of time. All Xen versions from 3.4 onwards are vulnerable. Xen versions 3.3 and earlier are vulnerable to an even wider class of attacks, due to them lacking preemption checks altogether in the affected code paths. Only x86 systems are affected. ARM systems are not affected. Only multi-vCPU x86 PV guests can leverage the vulnerability. x86 HVM or PVH guests as well as x86 single-vCPU PV ones cannot leverage the vulnerability.

6.5
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.08%
Vendor Advisory debian.org Vendor Advisory gentoo.org Vendor Advisory xen.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://www.debian.org/security/2018/dsa-4236 third party advisory vendor advisory
https://support.citrix.com/article/CTX235748 third party advisory
https://security.gentoo.org/glsa/201810-06 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2018/11/msg00013.html issue tracking mailing list third party advisory
http://xenbits.xen.org/xsa/advisory-264.html patch vendor advisory
http://www.securitytracker.com/id/1041201 vdb entry third party advisory
http://www.openwall.com/lists/oss-security/2018/06/27/10 mailing list third party advisory patch
http://www.securityfocus.com/bid/104570 vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2018-12891?
CVE-2018-12891 has been scored as a medium severity vulnerability.
How to fix CVE-2018-12891?
To fix CVE-2018-12891, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-12891 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2018-12891 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.