Syzbot CI

Subject	KVM: Fix+harden against bad uaccess using dying VM
Author	seanjc@google.com
Date	2026-10-01 20:22:25 +0000 UTC
Version
Cc	jmattson@google.com kvm@vger.kernel.org linux-kernel@vger.kernel.org linuxppc-dev@lists.ozlabs.org maddy@linux.ibm.com npiggin@gmail.com pbonzini@redhat.com seanjc@google.com

Patches (10)

Expand

Name	Content [All]
[PATCH v2 01/10] KVM: Reject user accesses to guest memory if current->mm != kvm->mm	[Body]
[PATCH v2 02/10] KVM: PPC: Flush/zap all memslots on kvm_arch_flush_shadow_all()	[Body]
[PATCH v2 03/10] KVM: x86: Unmap VMAs for KVM-internal memslots when the memslot is freed	[Body]
[PATCH v2 04/10] KVM: Disallow setting memslots when the VM is being destroyed	[Body]
[PATCH v2 05/10] KVM: Destroy memslots immediately after mmu_notifiers are unregistered	[Body]
[PATCH v2 06/10] KVM: WARN if KVM attempts to do guest-related uaccess with "wrong" process	[Body]
[PATCH v2 07/10] KVM: WARN and reject guest-based uaccess if VM is dying	[Body]
[PATCH v2 08/10] KVM: nVMX: Don't flush shadow VMCS12 to guest memory during vCPU teardown	[Body]
[PATCH v2 09/10] KVM: nVMX: Don't try to load eVMCS12 page when the VM is dying	[Body]
[PATCH v2 10/10] KVM: Pre-check uaccesses in KVM's APIs to read/write guest memory	[Body]

Series Summary

waiting

Status: waiting

Sessions

Session 2026-10-01

waiting

ID (for dev)	db59ef38-dc91-4eaa-bbd5-bf1d366d147d
Status	waiting

Test	Base	Patched	Verdict