First published: Wed Nov 21 2012(Updated: )
Xen 3.4 through 4.2, and possibly earlier versions, does not properly synchronize the p2m and m2p tables when the set_p2m_entry function fails, which allows local HVM guest OS administrators to cause a denial of service (memory consumption and assertion failure), aka "Memory mapping failure DoS vulnerability."
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
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 | |
Xen Xen | =4.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.