Wrong ordering of operations upon extending the per-domain event channel tracking table can cause a pointer to freed memory to be left in place, when the hypervisor is under memory pressure and XSM (Xen Security Module) is enabled. Malicious guest kernels could inject arbitrary events or corrupt other hypervisor state, possibly leading to code execution. References: http://seclists.org/oss-sec/2013/q2/17 Acknowledgements: Red Hat would like to thank the Xen project for reporting this issue.
Statement: Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor.
Fedora isn't vulnerable as we don't build xen with XSM enabled. However the source for xen-4.2.1-10.fc19, xen-4.2.1-10.fc18 and xen-4.1.4-7.fc17 include the patch.