First published: Wed Nov 21 2012(Updated: )
Xen 4.0 through 4.2, when running 32-bit x86 PV guests on 64-bit hypervisors, allows local guest OS administrators to cause a denial of service (infinite loop and hang or crash) via invalid arguments to GNTTABOP_get_status_frames, aka "Grant table hypercall infinite loop DoS vulnerability."
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
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-4539 is considered a high severity vulnerability due to its potential to cause a denial of service.
CVE-2012-4539 allows local guest OS administrators to induce an infinite loop and hang or crash the hypervisor.
CVE-2012-4539 affects Xen versions 4.0 through 4.2 when running 32-bit x86 PV guests on 64-bit hypervisors.
To mitigate CVE-2012-4539, ensure that the affected versions of Xen are updated to a patched version that addresses this vulnerability.
CVE-2012-4539 is not exploitable remotely as it requires local administrative access to the guest operating system.