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,
Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH 0/2] KVM: Fix a guest_memfd memslot UAF
Date: Fri, 5 Dec 2025 08:59:27 -0800 [thread overview]
Message-ID: <176494720872.296359.3976381514002984346.b4-ty@google.com> (raw)
In-Reply-To: <20251202020334.1171351-1-seanjc@google.com>
On Mon, 01 Dec 2025 18:03:32 -0800, Sean Christopherson wrote:
> Fix a UAF due to leaving a dangling guest_memfd memslot binding by
> disallowing clearing KVM_MEM_GUEST_MEMFD on a memslot. The intent was
> that guest_memfd memslots would be immutable (could only be deleted),
> but somewhat ironically we missed the case where KVM_MEM_GUEST_MEMFD
> itself is the only flag that's toggled.
>
> This is an ABI change, but I can't imagine anyone was relying on
> disappearing a guest_memfd memslot.
>
> [...]
Applied to kvm-x86 fixes (I'm feeling lucky with the ABI change).
[1/2] KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot
https://github.com/kvm-x86/linux/commit/9935df5333aa
[2/2] KVM: Harden and prepare for modifying existing guest_memfd memslots
https://github.com/kvm-x86/linux/commit/af62fe2494da
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2025-12-05 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 2:03 Sean Christopherson
2025-12-02 2:03 ` [PATCH 1/2] KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot Sean Christopherson
2025-12-02 2:03 ` [PATCH 2/2] KVM: Harden and prepare for modifying existing guest_memfd memslots Sean Christopherson
2025-12-02 15:27 ` [PATCH 0/2] KVM: Fix a guest_memfd memslot UAF Sean Christopherson
2025-12-05 16:59 ` 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=176494720872.296359.3976381514002984346.b4-ty@google.com \
--to=seanjc@google.com \
--cc=glider@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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®