From: Venkatesh Srinivas <venkateshs@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
digitaleric@google.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM: x86: work around infinite loop in microcode when #AC is delivered
Date: Tue, 10 Nov 2015 16:39:39 -0800 [thread overview]
Message-ID: <20151111003939.GA31855@google.com> (raw)
In-Reply-To: <1447158174-10484-2-git-send-email-pbonzini@redhat.com>
On Tue, Nov 10, 2015 at 01:22:52PM +0100, Paolo Bonzini wrote:
> From: Eric Northup <digitaleric@google.com>
>
> It was found that a guest can DoS a host by triggering an infinite
> stream of "alignment check" (#AC) exceptions. This causes the
> microcode to enter an infinite loop where the core never receives
> another interrupt. The host kernel panics pretty quickly due to the
> effects (CVE-2015-5307).
>
> Signed-off-by: Eric Northup <digitaleric@google.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Tested-by: Venkatesh Srinivas <venkateshs@google.com>
-- vs;
next prev parent reply other threads:[~2015-11-11 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:22 [PATCH 0/3] Infinite loops in microcode while running guests Paolo Bonzini
2015-11-10 12:22 ` [PATCH 1/3] KVM: x86: work around infinite loop in microcode when #AC is delivered Paolo Bonzini
2015-11-11 0:39 ` Venkatesh Srinivas [this message]
2015-11-10 12:22 ` [PATCH 2/3] KVM: svm: unconditionally intercept #DB Paolo Bonzini
2015-11-10 12:22 ` [PATCH 3/3] KVM: x86: rename update_db_bp_intercept to update_bp_intercept Paolo Bonzini
2015-11-10 15:38 ` [PATCH 0/3] Infinite loops in microcode while running guests Jan Kiszka
2015-11-10 16:09 ` Paolo Bonzini
2015-11-11 12:47 ` Austin S Hemmelgarn
2015-11-11 13:07 ` Paolo Bonzini
2015-11-11 13:12 ` Austin S Hemmelgarn
2015-11-12 14:08 ` Jan Kiszka
2015-11-12 14:37 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151111003939.GA31855@google.com \
--to=venkateshs@google.com \
--cc=digitaleric@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.