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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Xen | Xen | 3.4.0 (including) | 3.4.0 (including) |
| Xen | Xen | 3.4.1 (including) | 3.4.1 (including) |
| Xen | Xen | 3.4.2 (including) | 3.4.2 (including) |
| Xen | Xen | 3.4.3 (including) | 3.4.3 (including) |
| Xen | Xen | 3.4.4 (including) | 3.4.4 (including) |
| Xen | Xen | 4.0.0 (including) | 4.0.0 (including) |
| Xen | Xen | 4.0.1 (including) | 4.0.1 (including) |
| Xen | Xen | 4.0.2 (including) | 4.0.2 (including) |
| Xen | Xen | 4.0.3 (including) | 4.0.3 (including) |
| Xen | Xen | 4.0.4 (including) | 4.0.4 (including) |
| Xen | Xen | 4.1.0 (including) | 4.1.0 (including) |
| Xen | Xen | 4.1.1 (including) | 4.1.1 (including) |
| Xen | Xen | 4.1.2 (including) | 4.1.2 (including) |
| Xen | Xen | 4.1.3 (including) | 4.1.3 (including) |
| Xen | Xen | 4.2.0 (including) | 4.2.0 (including) |