CVE-2026-99340
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().
Properties
- Severity
- HIGH
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Cvss severity
- HIGH
- Cvss score
- 7.8
- Epss score
- 0.00215
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Last source
- FIRST EPSS
- Score
- 7.8
- Cvss version
- 3.1
- Cve id
- CVE-2026-99340
- Cvss vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- First seen by Signal
- 2026-11-19T15:26:52+00:00
- Name
- CVE-2026-99340
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published at
- 2026-11-19T15:17:45.113
- Last modified
- 2026-11-22T11:16:47.950
- Epss percentile
- 0.11909
Related research
Explore deeper with Ninja Signal's threat intelligence graph