On Fri, 30 Oct 2026 14:20:48 -0700, Sean Christopherson wrote:
> Stupid SMM. Patches 1-3 need to go to 7.4, everything else can and should
> wait.
>
> Fix a class of bugs (limited to nested VMX, as far as we know) where KVM can
> corrupt an unrelated process' memory if KVM (attempts to) write to guest
> memory
> during VM destruction. Because current->mm usually isn't kvm->mm when a VM is
> dying, e.g. because the associated kvm->mm process has already exited, writing
> to what KVM thinks is guest memory will corrupt the current address space if
> the associated userspace address happens to be writable in the victim.
>
> [...]
Applied patch 1-3 to kvm-x86 fixes. I'll probably create a dedicated topic
branch for the rest based on a later -rc.
[01/23] KVM: Reject user accesses to guest memory if current->mm != kvm->mm
https://github.com/kvm-x86/linux/commit/2520694e6048
[02/23] KVM: nVMX: Don't force a full nested VM-Exit when destroying a vCPU
https://github.com/kvm-x86/linux/commit/99872af7b904
[03/23] KVM: PPC: Flush/zap all memslots on kvm_arch_flush_shadow_all()
https://github.com/kvm-x86/linux/commit/93862ef1afdd
--
https://github.com/kvm-x86/linux/tree/next
