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 XAPI | =3.4.0 | |
Xen XAPI | =3.4.1 | |
Xen XAPI | =3.4.2 | |
Xen XAPI | =3.4.3 | |
Xen XAPI | =3.4.4 | |
Xen XAPI | =4.0.0 | |
Xen XAPI | =4.0.1 | |
Xen XAPI | =4.0.2 | |
Xen XAPI | =4.0.3 | |
Xen XAPI | =4.0.4 | |
Xen XAPI | =4.1.0 | |
Xen XAPI | =4.1.1 | |
Xen XAPI | =4.1.2 | |
Xen XAPI | =4.1.3 | |
Xen XAPI | =4.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-4537 has been classified as a denial of service vulnerability that could lead to memory consumption and assertion failure.
To mitigate CVE-2012-4537, users should upgrade to the latest available version of Xen that contains the necessary patches.
CVE-2012-4537 affects Xen versions from 3.4 to 4.2, including specific releases like 3.4.0 to 4.2.0.
An attacker with local administrative access to a guest HVM OS can exploit CVE-2012-4537 to cause a denial of service.
Yes, CVE-2012-4537 relates to improper synchronization of memory mapping tables, which can lead to significant memory issues.