From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sean Christopherson <seanjc@google.com>
Cc: "IP over Parrots (with QoS)" <opensource@rfc2549.ca>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: 6.1.y status: 2abd5287f083 ("KVM: x86: Check for invalid/obsolete root *after* making MMU pages available") / CVE-2026-64561
Date: Wed, 12 Aug 2026 14:07:19 +0900 [thread overview]
Message-ID: <anv_QkW6fLzPy1_z@google.com> (raw)
In-Reply-To: <antH6ysN2SPR2gyV@google.com>
On (26/08/11 09:03), Sean Christopherson wrote:
> +Sergey
>
[..]
> > Now planned. The fix doesn't apply cleanly to 6.1, and the resolving the conflict
> > isn't super straightforward (though it's not thaaaat bad either).
> >
> > https://lore.kernel.org/all/anpVAhjqvBvIuoa0@google.com
> >
> > > The security tracker [1] for the Debian 12 stable kernel (6.1.y)
> > > shows a vulnerable status.
> > >
> > > I do not have a backport to offer, so this is just an inquiry.
> > > I am happy to build and test a candidate on 6.1 if that would
> > > be useful.
> >
> > I'll post a patch today and Cc you (unless I get goldfish brain, in which case
> > I apologize in advance).
>
> Actually, duh, Sasha already posted backports[*], and his approach is much better
> than manually resolving the conflicts. Testing that now, I'll ACK those assuming
> all goes well.
>
> [*] https://lore.kernel.org/all/20260730121535.2208491-1-sashal@kernel.org
Good news and good job! Thanks.
next prev parent reply other threads:[~2026-08-12 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:41 6.1.y status: 2abd5287f083 ("KVM: x86: Check for invalid/obsolete root *after* making MMU pages available") / CVE-2026-64561 IP over Parrots (with QoS)
2026-08-11 14:44 ` Sean Christopherson
2026-08-11 16:03 ` Sean Christopherson
2026-08-12 5:07 ` Sergey Senozhatsky [this message]
2026-08-11 15:24 ` Paolo Bonzini
2026-08-12 1:08 ` IP over Parrots (with QoS)
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=anv_QkW6fLzPy1_z@google.com \
--to=senozhatsky@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=opensource@rfc2549.ca \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--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