diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2014-03-28 20:41:50 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-05-13 13:32:48 +0200 |
| commit | f8944acc97ceebf902e5b26b900aefef987ab4be (patch) | |
| tree | 411f02232c0df2c94d4df4e2a0bc844d67b13ed1 /arch/mips | |
| parent | 9e66614b8c36b8d96bf7b271a3eacada1e4c589d (diff) | |
| download | kernel-common-f8944acc97ceebf902e5b26b900aefef987ab4be.tar.gz kernel-common-f8944acc97ceebf902e5b26b900aefef987ab4be.tar.bz2 kernel-common-f8944acc97ceebf902e5b26b900aefef987ab4be.zip | |
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>
Diffstat (limited to 'arch/mips')
0 files changed, 0 insertions, 0 deletions