]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
KVM: x86: Add LAPIC guard in kvm_apic_write_nodecode()
authorxuanqingshi <1356292400@qq.com>
Fri, 6 Mar 2026 09:12:32 +0000 (17:12 +0800)
committerSean Christopherson <seanjc@google.com>
Thu, 12 Mar 2026 16:11:40 +0000 (09:11 -0700)
commit26c9bfc0fac240540581cfbe58031b412f98aaf8
tree579e9eeef21df7fa021551ca4ddf3deede484ed7
parentd216449f253c7039c3e6a0276279c117a5198ce0
KVM: x86: Add LAPIC guard in kvm_apic_write_nodecode()

kvm_apic_write_nodecode() dereferences vcpu->arch.apic without first
checking whether the in-kernel LAPIC has been initialized.  If it has
not (e.g. the vCPU was created without an in-kernel LAPIC), the
dereference results in a NULL pointer access.

While APIC-write VM-Exits are not expected to occur on a vCPU without
an in-kernel LAPIC, kvm_apic_write_nodecode() should be robust against
such a scenario as a defense-in-depth measure, e.g. to guard against
KVM bugs or CPU errata that could generate a spurious APIC-write
VM-Exit.

Use KVM_BUG_ON() with lapic_in_kernel() instead of a simple
WARN_ON_ONCE(), as suggested by Sean Christopherson, so that KVM
kills the VM outright rather than letting it continue in a broken
state.

Found by a VMCS-targeted fuzzer based on syzkaller.

Signed-off-by: xuanqingshi <1356292400@qq.com>
Link: https://patch.msgid.link/tencent_7A9F1B4D75468C0CF5DE1B6902038C948B07@qq.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
arch/x86/kvm/lapic.c