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,
Naveen N Rao <naveen@kernel.org>, Atish Patra <atishp@meta.com>
Subject: [PATCH v2 0/3] KVM: SVM: Fix AVIC Physical ID table UAF
Date: Wed, 23 Sep 2026 08:51:05 -0700 [thread overview]
Message-ID: <20260923155108.1550622-1-seanjc@google.com> (raw)
Naveen's fix to clear AVIC Physical ID table entries if vCPU creation fails,
to ensure the CPU doesn't access the freed virtual APIC state.
v2: Add prep patches to consolidate the table bounds checks.
v1: https://lore.kernel.org/all/20260903062856.2090499-1-naveen@kernel.org
Naveen N Rao (1):
KVM: SVM: Clear AVIC Physical ID table entry if vCPU creation fails
Sean Christopherson (2):
KVM: SVM: Add paranoid helper for checking if vCPU is AVIC-addressable
KVM: SVM: Use "is AVIC-addressable" helper to sanity check
load()/put()
arch/x86/kvm/svm/avic.c | 22 ++++++++++++++++------
arch/x86/kvm/svm/svm.c | 6 +++++-
arch/x86/kvm/svm/svm.h | 1 +
3 files changed, 22 insertions(+), 7 deletions(-)
base-commit: d4b7fb647204f0c81dfeae2d1a708e4d858e0c94
--
2.55.0.1082.g2b9226bbc0-goog
next reply other threads:[~2026-09-23 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 15:51 Sean Christopherson [this message]
2026-09-23 15:51 ` [PATCH v2 1/3] KVM: SVM: Add paranoid helper for checking if vCPU is AVIC-addressable Sean Christopherson
2026-09-24 11:16 ` Naveen N Rao
2026-09-23 15:51 ` [PATCH v2 2/3] KVM: SVM: Use "is AVIC-addressable" helper to sanity check load()/put() Sean Christopherson
2026-09-24 11:16 ` Naveen N Rao
2026-09-23 15:51 ` [PATCH v2 3/3] KVM: SVM: Clear AVIC Physical ID table entry if vCPU creation fails Sean Christopherson
2026-09-24 11:21 ` Naveen N Rao
2026-09-24 13:55 ` 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=20260923155108.1550622-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=atishp@meta.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen@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
all inboxes | Powered by JetHome®