From: "Radim Krčmář" <rkrcmar@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Jim Mattson <jmattson@google.com>,
Wincy Van <fanwenyi0529@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>
Subject: [PATCH 0/2] KVM: nVMX: msr bitmaps fixes
Date: Mon, 8 Aug 2016 20:16:21 +0200 [thread overview]
Message-ID: <20160808181623.12132-1-rkrcmar@redhat.com> (raw)
Jim found several bugs that allowed L2 to read L0's x2APIC MSRs and write to
TPR, EOI, and SELF_IPI, in the worst case.
The fix is split into two patches as possible causes were introduced by
two different commits.
I have not Cc'd stable as the patches are quite long and nVMX is not
considered to be ready for production, yet.
Radim Krčmář (2):
KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
KVM: nVMX: postpone VMCS changes on MSR_IA32_APICBASE write
arch/x86/kvm/vmx.c | 120 +++++++++++++++++++++++++----------------------------
1 file changed, 57 insertions(+), 63 deletions(-)
--
2.9.2
next reply other threads:[~2016-08-08 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 18:16 Radim Krčmář [this message]
2016-08-08 18:16 ` [PATCH 1/2] KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC Radim Krčmář
2016-08-09 9:32 ` Yang Zhang
2016-08-09 10:19 ` Wincy Van
2016-08-10 5:52 ` Yang Zhang
2016-08-09 12:23 ` Radim Krčmář
2016-08-10 5:55 ` Yang Zhang
2016-08-16 2:53 ` Wanpeng Li
2016-08-08 18:16 ` [PATCH 2/2] KVM: nVMX: postpone VMCS changes on MSR_IA32_APICBASE write Radim Krčmář
2016-08-12 6:07 ` Wanpeng Li
2016-08-12 9:44 ` Radim Krčmář
2016-08-12 10:14 ` Wanpeng Li
2016-08-12 11:39 ` Radim Krčmář
2016-08-15 5:19 ` Wanpeng Li
2016-08-15 14:31 ` Radim Krčmář
2016-08-16 2:43 ` Wanpeng Li
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=20160808181623.12132-1-rkrcmar@redhat.com \
--to=rkrcmar@redhat.com \
--cc=bsd@redhat.com \
--cc=fanwenyi0529@gmail.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).