First published: Wed Nov 21 2012(Updated: )
Xen 3.4 through 4.2, and possibly earlier versions, allows local guest OS administrators to cause a denial of service (Xen infinite loop and physical CPU consumption) by setting a VCPU with an "inappropriate deadline."
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
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.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-4535 is considered to be of medium severity due to its potential to cause denial of service.
CVE-2012-4535 allows local guest OS administrators to create an infinite loop leading to physical CPU resource consumption.
CVE-2012-4535 affects Xen versions from 3.4 through 4.2, with potential impact on earlier versions.
To fix CVE-2012-4535, it is recommended to upgrade to the latest version of Xen that resolves this vulnerability.
Local guest OS administrators are at risk from CVE-2012-4535 as they can exploit this vulnerability to cause denial of service.