KVM: ioapic: fix assignment of ioapic->rtc_status.pending_eoi (CVE-2014-0155)
authorPaolo Bonzini <pbonzini@redhat.com>
Fri, 28 Mar 2014 19:41:50 +0000 (20:41 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 13 May 2014 11:32:48 +0000 (13:32 +0200)
commitf8944acc97ceebf902e5b26b900aefef987ab4be
tree411f02232c0df2c94d4df4e2a0bc844d67b13ed1
parent9e66614b8c36b8d96bf7b271a3eacada1e4c589d
KVM: ioapic: fix assignment of ioapic->rtc_status.pending_eoi (CVE-2014-0155)

commit 5678de3f15010b9022ee45673f33bcfc71d47b60 upstream.

QE reported that they got the BUG_ON in ioapic_service to trigger.
I cannot reproduce it, but there are two reasons why this could happen.

The less likely but also easiest one, is when kvm_irq_delivery_to_apic
does not deliver to any APIC and returns -1.

Because irqe.shorthand == 0, the kvm_for_each_vcpu loop in that
function is never reached.  However, you can target the similar loop in
kvm_irq_delivery_to_apic_fast; just program a zero logical destination
address into the IOAPIC, or an out-of-range physical destination address.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
virt/kvm/ioapic.c