CVE Feed
7.8 High

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Take SRCU in kvmzapgfnrange() kvmzapgfnrange() walks memslots…

CVE-2026-99340

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Take SRCU in kvmzapgfnrange() kvmzapgfnrange() walks memslots and rmaps and may drop mmulock to reschedule. Callers that do not already hold kvm->srcu (or slotslock) can race with memslot deletion: synchronizesrcuexpedited() does not wait, kvmfreememslot() 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 slotrmapwalknext+0x82/0x1c0 Read of size 8 at addr ffffc900005c1008 Call Trace: slotrmapwalknext+0x82/0x1c0 kvmrmapzapgfnrange+0x17a/0x280 kvmzapgfnrange+0x2a6/0x6a0 kvmvfiosetattr+0x576/0x770 kvmdeviceioctl+0x1ff/0x3b0 Take SRCU inside kvmzapgfnrange() 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 kvmsetorclearapicvinhibit().

Assessment

CVSS
7.8 (v3.1)
Severity
High
EPSS
0.22% chance of exploitation in the next 30 days
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
19 November 2026
Last updated
22 November 2026
Affected
Linux · Linux
Assigner
Linux

CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99340