Three issues were found: * s->next_packet is read from wire as an index into s->rx[]. * s->tx_fifo_len is read from the wire and later used as an index into s->tx_fifo[] when a DATA command is issued by the guest. * s->tx_frame_len is read from the wire and can later used as an index into s->tx_fifo[] for memset() when a DATA command is issued by the guest. An user able to alter the savevm data (either on the disk or over the wire during migration) could use this flaw to to corrupt QEMU process memory on the (destination) host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. References: http://lists.gnu.org/archive/html/qemu-devel/2013-12/msg00403.html http://lists.gnu.org/archive/html/qemu-devel/2013-12/msg00414.html http://lists.gnu.org/archive/html/qemu-devel/2013-12/msg00404.html
Statement: Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6