From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, pbonzini@redhat.com,
gregkh@linuxfoundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, 0wn@theori.io,
mlevitsk@redhat.com, jmattson@google.com,
Nicholas Dudar <main.kalliope@gmail.com>
Subject: Re: [PATCH v2 6.1.y 0/3] KVM: nVMX: backport virtual-APIC host NULL-deref fix
Date: Mon, 22 Jun 2026 19:07:11 -0700 [thread overview]
Message-ID: <ajnqTyhKNqOjKnzF@google.com> (raw)
In-Reply-To: <20260621133722.0003.sashal@kernel.org>
On Sun, Jun 21, 2026, Sasha Levin wrote:
> > This series backports the fix for a guest-triggerable host NULL pointer
> > dereference in nested-VMX virtual-APIC handling. The bug is present in
> > 6.1.y and fixed in 6.6.y and later.
>
> Queued the 3-patch series for 6.1, thanks.
Backports LGTM, thanks Nicholas!
prev parent reply other threads:[~2026-06-23 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 20:31 [PATCH v2 6.1.y 0/3] KVM: nVMX: backport virtual-APIC host NULL-deref fix Nicholas Dudar
2026-06-19 20:31 ` [PATCH v2 6.1.y 1/3] KVM: nVMX: Add a helper to get highest pending from Posted Interrupt vector Nicholas Dudar
2026-06-23 2:01 ` Sean Christopherson
2026-06-23 3:03 ` Admin
2026-06-19 20:31 ` [PATCH v2 6.1.y 2/3] KVM: nVMX: Check for pending posted interrupts when looking for nested events Nicholas Dudar
2026-06-19 20:31 ` [PATCH v2 6.1.y 3/3] KVM: nVMX: Fold requested virtual interrupt check into has_nested_events() Nicholas Dudar
2026-06-21 13:47 ` [PATCH v2 6.1.y 0/3] KVM: nVMX: backport virtual-APIC host NULL-deref fix Sasha Levin
2026-06-23 2:07 ` Sean Christopherson [this message]
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=ajnqTyhKNqOjKnzF@google.com \
--to=seanjc@google.com \
--cc=0wn@theori.io \
--cc=gregkh@linuxfoundation.org \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=main.kalliope@gmail.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox