Description
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Take SRCU in kvm_zap_gfn_range() kvm_zap_gfn_range() walks memslots and rmaps and may drop mmu_lock to reschedule. Callers that do not already hold kvm->srcu (or slots_lock) can race with memslot deletion: synchronize_srcu_expedited() does not wait, kvm_free_memslot() frees the old slot and its rmap, and the zap resumes on freed memory. The VFIO noncoherent-DMA path hits this by zapping the entire GPA space without SRCU. KASAN reported: BUG: KASAN: vmalloc-out-of-bounds in slot_rmap_walk_next+0x82/0x1c0 Read of size 8 at addr ffffc900005c1008 Call Trace: slot_rmap_walk_next+0x82/0x1c0 __kvm_rmap_zap_gfn_range+0x17a/0x280 kvm_zap_gfn_range+0x2a6/0x6a0 kvm_vfio_set_attr+0x576/0x770 kvm_device_ioctl+0x1ff/0x3b0 Take SRCU inside kvm_zap_gfn_range() so every caller is covered. Nesting with an existing kvm->srcu critical section is fine; the helper uses a local index. Drop the now-redundant SRCU pair from __kvm_set_or_clear_apicv_inhibit().
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
362ff6dca5416e20646badf09394b9a8bfc000db to < 9d119b4921ac74bc606917fd274c10c966fa5b72affected362ff6dca5416e20646badf09394b9a8bfc000db to < ec9df57c8e00f189d58d927cc9a1f49592f687afaffected362ff6dca5416e20646badf09394b9a8bfc000db to < e34057e59ed784a37657835aac9f54eec0864342affected362ff6dca5416e20646badf09394b9a8bfc000db to < b59a87c1ba3c347e8aec5f932eb7abf13064fd62affected
Linux Linux
Default version status: affected
6.7affected0 to < 6.7unaffected6.12.117 to ≤ 6.12.*unaffected6.18.61 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected