First published: Mon Jun 15 2015(Updated: )
The compat_iret function in Xen 3.1 through 4.5 iterates the wrong way through a loop, which allows local 32-bit PV guest administrators to cause a denial of service (large loop and system hang) via a hypercall_iret call with EFLAGS.VM set.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =3.1.3 | |
Xen xen-unstable | =3.1.4 | |
Xen xen-unstable | =3.2.0 | |
Xen xen-unstable | =3.2.1 | |
Xen xen-unstable | =3.2.2 | |
Xen xen-unstable | =3.2.3 | |
Xen xen-unstable | =3.3.0 | |
Xen xen-unstable | =3.3.1 | |
Xen xen-unstable | =3.3.2 | |
Xen xen-unstable | =3.4.0 | |
Xen xen-unstable | =3.4.1 | |
Xen xen-unstable | =3.4.2 | |
Xen xen-unstable | =3.4.3 | |
Xen xen-unstable | =3.4.4 | |
Xen xen-unstable | =4.0.0 | |
Xen xen-unstable | =4.0.1 | |
Xen xen-unstable | =4.0.2 | |
Xen xen-unstable | =4.0.3 | |
Xen xen-unstable | =4.0.4 | |
Xen xen-unstable | =4.1.0 | |
Xen xen-unstable | =4.1.1 | |
Xen xen-unstable | =4.1.2 | |
Xen xen-unstable | =4.1.3 | |
Xen xen-unstable | =4.1.4 | |
Xen xen-unstable | =4.1.5 | |
Xen xen-unstable | =4.1.6.1 | |
Xen xen-unstable | =4.2.0 | |
Xen xen-unstable | =4.2.1 | |
Xen xen-unstable | =4.2.2 | |
Xen xen-unstable | =4.2.3 | |
Xen xen-unstable | =4.3.0 | |
Xen xen-unstable | =4.3.1 | |
Xen xen-unstable | =4.3.4 | |
Xen xen-unstable | =4.4.0 | |
Xen xen-unstable | =4.4.0-rc1 | |
Xen xen-unstable | =4.4.1 | |
Xen xen-unstable | =4.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-4164 has a severity rating that could lead to a denial of service due to a large loop and potential system hang.
To fix CVE-2015-4164, it is recommended to upgrade to a later version of Xen that addresses this vulnerability.
CVE-2015-4164 affects Xen versions 3.1 through 4.5, including specific minor versions within that range.
CVE-2015-4164 allows local 32-bit PV guest administrators to cause a denial of service via a specific hypercall.
No specific workaround is documented for CVE-2015-4164; upgrading to a patched version is the best course of action.