CVE-2026-99340
Received Received - Intake

Race Condition in Linux Kernel KVM Subsystem

Vulnerability report for CVE-2026-99340, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: kernel.org

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in the Linux kernel's KVM (Kernel-based Virtual Machine) component. It involves a race condition in the kvm_zap_gfn_range() function where memslot deletion can occur while the function is still accessing freed memory. The issue arises because some callers do not hold the required SRCU (Sleepable Read-Copy-Update) lock, leading to a use-after-free scenario detected by KASAN.

Detection Guidance

This vulnerability is specific to the Linux kernel's KVM (Kernel-based Virtual Machine) component. Detection requires checking the kernel version and KVM module behavior. Use commands like 'uname -a' to check kernel version and 'lsmod | grep kvm' to verify KVM modules are loaded. Monitor kernel logs for KASAN errors or crashes related to KVM operations.

Impact Analysis

This vulnerability could allow an attacker with access to a virtual machine to trigger a use-after-free error, potentially causing a system crash or privilege escalation. It affects systems using KVM with VFIO noncoherent-DMA, enabling unauthorized memory access or denial of service.

Mitigation Strategies

Apply the latest kernel patches from your Linux distribution to resolve the issue. If immediate patching is not possible, consider disabling KVM virtualization temporarily until the patch is applied. Monitor vendor advisories for updates and test patches in a non-production environment before deployment.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-99340. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...