First published: Mon May 13 2013(Updated: )
Xen 3.1 through 4.x, when running 64-bit hosts on Intel CPUs, does not clear the NT flag when using an IRET after a SYSENTER instruction, which allows PV guest users to cause a denial of service (hypervisor crash) by triggering a #GP fault, which is not properly handled by another IRET instruction.
Credit: secalert@redhat.com
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.2.0 | |
Xen xen-unstable | =4.2.1 | |
Xen xen-unstable | =4.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1917 has a severity rating that indicates it can cause a denial of service through a hypervisor crash.
To fix CVE-2013-1917, update your Xen software to a version that addresses this vulnerability.
CVE-2013-1917 affects Xen versions 3.1 through 4.x running on 64-bit hosts with Intel CPUs.
CVE-2013-1917 can be exploited by PV guest users to trigger a hypervisor crash.
Currently, the best solution for CVE-2013-1917 is to apply the latest security patches and updates for your Xen installation.