Skip to main content
VulnerabilityPublished

CVE-2026-99340: Linux kernel · KVM: x86: Take SRCU in kvm_zap_gfn_range()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ec9df57c8e00f189d58d927cc9a1f49592f687af : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:34 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ec9df57c8e00f189d58d927cc9a1f49592f687af, e34057e59ed784a37657835aac9f54eec0864342, b59a87c1ba3c347e8aec5f932eb7abf13064fd62 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to ec9df57c8e00f189d58d927cc9a1f49592f687af, e34057e59ed784a37657835aac9f54eec0864342, b59a87c1ba3c347e8aec5f932eb7abf13064fd62 or 9d119b4921ac74bc606917fd274c10c966fa5b72.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 362ff6dca5416e20646badf09394b9a8bfc000db, < ec9df57c8e00f189d58d927cc9a1f49592f687af
Fixed in
  • ec9df57c8e00f189d58d927cc9a1f49592f687af
LinuxLinuxAffected
  • ≥ 362ff6dca5416e20646badf09394b9a8bfc000db, < e34057e59ed784a37657835aac9f54eec0864342
Fixed in
  • e34057e59ed784a37657835aac9f54eec0864342
LinuxLinuxAffected
  • ≥ 362ff6dca5416e20646badf09394b9a8bfc000db, < b59a87c1ba3c347e8aec5f932eb7abf13064fd62
Fixed in
  • b59a87c1ba3c347e8aec5f932eb7abf13064fd62
LinuxLinuxAffected
  • ≥ 362ff6dca5416e20646badf09394b9a8bfc000db, < 9d119b4921ac74bc606917fd274c10c966fa5b72
Fixed in
  • 9d119b4921ac74bc606917fd274c10c966fa5b72
LinuxLinuxAffected
  • =6.7
Fixed in–

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().

References

Community reviews

Loading reviews…