All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 stable@vger.kernel.org, senozhatsky@chromium.org
Subject: Re: [PATCH 5.10.y 00/17] KVM: fixes for CVE-2026-46113 and related issues
Date: Thu, 23 Jul 2026 15:41:31 +0900	[thread overview]
Message-ID: <amG3L3Tkmxuz_7S3@google.com> (raw)

> Sasha, Greg,
> 
> this is the backport to 5.10 for the above CVE.  Similar to 5.15, the
> fix was relatively simple upstream but only due to years of refactoring
> and cleaning up of the code; fixing from scratch is not really feasible
> so start by applying the patches that are needed.

Similary to 5.15 patchset, has this series stuck?

             reply	other threads:[~2026-07-23  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  6:41 Sergey Senozhatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 11:26 [PATCH 5.10.y 00/17] KVM: fixes for CVE-2026-46113 and related issues Paolo Bonzini

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=amG3L3Tkmxuz_7S3@google.com \
    --to=senozhatsky@chromium.org \
    --cc=20260626112634.1778506-1-pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.