From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jinwoo Lee <rkskek9254@gmail.com>,
Stefan Teodorescu <fane@google.com>
Subject: [PATCH v2 0/2] KVM: x86: Ensure userspace can't run L2 with stale PFNs
Date: Mon, 21 Sep 2026 14:16:06 -0700 [thread overview]
Message-ID: <20260921211608.1030158-1-seanjc@google.com> (raw)
Fix a class of bugs where KVM (a) lets userspace run L2 with potentially stale
PFNs and (b) fails to set kvm_run appropriately and so could unintentionally
cause a well-behaved VMM to run afoul of (a).
v2:
- Re-pend KVM_REQ_GET_NESTED_STATE_PAGES in the common vcpu_enter_guest()
path.
- Fix the kvm_run bug(s).
v1: https://lore.kernel.org/all/20260813043932.3214460-1-rkskek9254@gmail.com
Sean Christopherson (2):
KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails
KVM: x86: Fill kvm_run exit fields in common get_nested_state_pages()
error paths
arch/x86/kvm/svm/nested.c | 7 +------
arch/x86/kvm/vmx/nested.c | 15 +++++----------
arch/x86/kvm/x86.c | 4 ++++
3 files changed, 10 insertions(+), 16 deletions(-)
base-commit: 70c944caf570fda2d79baa71435589a8db39f048
--
2.55.0.1082.g2b9226bbc0-goog
next reply other threads:[~2026-09-21 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 21:16 Sean Christopherson [this message]
2026-09-21 21:16 ` [PATCH v2 1/2] KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails Sean Christopherson
2026-09-21 21:16 ` [PATCH v2 2/2] KVM: x86: Fill kvm_run exit fields in common get_nested_state_pages() error paths Sean Christopherson
2026-09-24 21:52 ` [PATCH v2 0/2] KVM: x86: Ensure userspace can't run L2 with stale PFNs 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=20260921211608.1030158-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=fane@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkskek9254@gmail.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