The IRQ setup in Xen 4.2.x and 4.3.x, when using device passthrough and configured to support a large number of CPUs, frees certain memory that may still be intended for use, which allows local guest administrators to cause a denial of service (memory corruption and hypervisor crash) and possibly execute arbitrary code via vectors related to an out-of-memory error that triggers a (1) use-after-free or (2) double free.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Xen | Xen | 4.2.0 (including) | 4.2.0 (including) |
| Xen | Xen | 4.2.1 (including) | 4.2.1 (including) |
| Xen | Xen | 4.2.2 (including) | 4.2.2 (including) |
| Xen | Xen | 4.2.3 (including) | 4.2.3 (including) |
| Xen | Xen | 4.3.0 (including) | 4.3.0 (including) |
| Xen | Xen | 4.3.1 (including) | 4.3.1 (including) |
| Xen | Ubuntu | devel | * |
| Xen | Ubuntu | precise | * |
| Xen | Ubuntu | quantal | * |
| Xen | Ubuntu | raring | * |
| Xen | Ubuntu | saucy | * |
| Xen | Ubuntu | upstream | * |
| Xen-3.3 | Ubuntu | upstream | * |