First published: Thu Dec 13 2012(Updated: )
The XENMEM_exchange handler in Xen 4.2 and earlier does not properly check the memory address, which allows local PV guest OS administrators to cause a denial of service (crash) or possibly gain privileges via unspecified vectors that overwrite memory in the hypervisor reserved range.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Xen Xen | <=4.2.0 | |
Xen Xen | =3.0.2 | |
Xen Xen | =3.0.3 | |
Xen Xen | =3.0.4 | |
Xen Xen | =3.1.3 | |
Xen Xen | =3.1.4 | |
Xen Xen | =3.2.0 | |
Xen Xen | =3.2.1 | |
Xen Xen | =3.2.2 | |
Xen Xen | =3.2.3 | |
Xen Xen | =3.3.0 | |
Xen Xen | =3.3.1 | |
Xen Xen | =3.3.2 | |
Xen Xen | =3.4.0 | |
Xen Xen | =3.4.1 | |
Xen Xen | =3.4.2 | |
Xen Xen | =3.4.3 | |
Xen Xen | =3.4.4 | |
Xen Xen | =4.0.0 | |
Xen Xen | =4.0.1 | |
Xen Xen | =4.0.2 | |
Xen Xen | =4.0.3 | |
Xen Xen | =4.0.4 | |
Xen Xen | =4.1.0 | |
Xen Xen | =4.1.1 | |
Xen Xen | =4.1.2 | |
Xen Xen | =4.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.