linux-kernel - Re: [PATCH 0/2] KVM: Fix a guest

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176494720872.296359.3976381514002984346.b4-ty@google.com>
Date: Fri,  5 Dec 2025 08:59:27 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Alexander Potapenko <glider@...gle.com>
Subject: Re: [PATCH 0/2] KVM: Fix a guest_memfd memslot UAF

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