From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
zyr_ms@outlook.com, Sean Christopherson <seanjc@google.com>
Subject: [PATCH 0/2] KVM: Fix a lurking bug in kvm_clear_guest()
Date: Thu, 29 Aug 2024 12:14:11 -0700 [thread overview]
Message-ID: <20240829191413.900740-1-seanjc@google.com> (raw)
Fix a bug in kvm_clear_guest() where it would write beyond the target
page _if_ handed a gpa+len that would span multiple pages. Luckily, the
bug is unhittable in the current code base as all users ensure the
gpa+len is bound to a single page.
Patch 2 hardens the underlying single page APIs to guard against a bad
offset+len, e.g. so that bugs like the one in kvm_clear_guest() are noisy
and don't escalate to an out-of-bounds access.
Verified and tested by hacking KVM to use kvm_clear_guest() when zeroing
all three pages used for KVM's hidden TSS.
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index f18c2d8c7476..ce64e490e9c7 100644
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -3872,14 +3872,17 @@ bool __vmx_guest_state_valid(struct kvm_vcpu *vcpu)
static int init_rmode_tss(struct kvm *kvm, void __user *ua)
{
- const void *zero_page = (const void *) __va(page_to_phys(ZERO_PAGE(0)));
+ // const void *zero_page = (const void *) __va(page_to_phys(ZERO_PAGE(0)));
u16 data;
- int i;
+ // int i;
- for (i = 0; i < 3; i++) {
- if (__copy_to_user(ua + PAGE_SIZE * i, zero_page, PAGE_SIZE))
- return -EFAULT;
- }
+ if (kvm_clear_guest(kvm, to_kvm_vmx(kvm)->tss_addr, PAGE_SIZE * 3))
+ return -EFAULT;
+
+ // for (i = 0; i < 3; i++) {
+ // if (__copy_to_user(ua + PAGE_SIZE * i, zero_page, PAGE_SIZE))
+ // return -EFAULT;
+ // }
data = TSS_BASE_SIZE + TSS_REDIRECTION_SIZE;
if (__copy_to_user(ua + TSS_IOPB_BASE_OFFSET, &data, sizeof(u16)))
Sean Christopherson (2):
KVM: Write the per-page "segment" when clearing (part of) a guest page
KVM: Harden guest memory APIs against out-of-bounds accesses
virt/kvm/kvm_main.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
base-commit: 15e1c3d65975524c5c792fcd59f7d89f00402261
--
2.46.0.469.g59c65b2a67-goog
next reply other threads:[~2024-08-29 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 19:14 Sean Christopherson [this message]
2024-08-29 19:14 ` [PATCH 1/2] KVM: Write the per-page "segment" when clearing (part of) a guest page Sean Christopherson
2024-08-29 19:14 ` [PATCH 2/2] KVM: Harden guest memory APIs against out-of-bounds accesses Sean Christopherson
2024-09-10 4:56 ` [PATCH 0/2] KVM: Fix a lurking bug in kvm_clear_guest() Sean Christopherson
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=20240829191413.900740-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=zyr_ms@outlook.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
all inboxes | Powered by JetHome®