Xen 4.2.x, 4.1.x, and previous versions, when the hypervisor is running "under memory pressure" and the Xen Security Module (XSM) is enabled, uses the wrong ordering of operations when extending the per-domain event channel tracking table, which causes a use-after-free and allows local guest kernels to inject arbitrary events and gain privileges via unspecified vectors.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
xen xen 4.1.2 |
||
xen xen 4.1.1 |
||
xen xen 3.3.1 |
||
xen xen 3.2.3 |
||
xen xen 3.1.3 |
||
xen xen 3.0.2 |
||
xen xen 4.2.0 |
||
xen xen 4.2.1 |
||
xen xen 4.0.3 |
||
xen xen 4.0.2 |
||
xen xen 3.2.2 |
||
xen xen 3.1.4 |
||
xen xen 4.1.4 |
||
xen xen 4.1.3 |
||
xen xen 4.0.1 |
||
xen xen 4.0.0 |
||
xen xen 3.2.0 |
||
xen xen 3.0.4 |
||
xen xen 3.4.2 |
||
xen xen 3.4.0 |
||
xen xen 3.4.4 |
||
xen xen 3.4.1 |
||
xen xen 4.1.0 |
||
xen xen 4.0.4 |
||
xen xen 3.3.2 |
||
xen xen 3.2.1 |
||
xen xen 3.0.3 |
||
xen xen 3.3.0 |
||
xen xen 3.4.3 |
Vulmon