5028 matches found
CVE-2026-64513
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally recompute CR8 intercept on PPR update The TPRTHRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject...
CVE-2026-64308
CVE-2026-64308 affects the Linux kernel's crypto:ccp module, which handles AMD SEV (Secure Encrypted Virtualization) and SNP (Secure Nested Paging). The root cause is that the ioctl(SNP_VLEK_LOAD) handler performed a pointless init/shutdown wrapper—firmware deletes the VLEK on SNP_SHUTDOWN anyway...
EUVD-2026-49019
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPCONFIG Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and ze...
CVE-2026-64287 KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Bound usedlrs when flushing the pKVM hyp vCPU flushhypvcpu copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use usedlrs as their loop bound and expect it to...
CVE-2026-64287
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Bound usedlrs when flushing the pKVM hyp vCPU flushhypvcpu copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use usedlrs as their loop bound and expect it to...
EUVD-2026-49000
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Avoid dereferencing NULL VNCR pseudo-TLB VNCR TLB invalidation occurs from MMU notifiers or TLBI instructions, and either can race against a vcpu not being onlined yet no pseudo-TLB allocated. Similarly, the TLB...
CVE-2026-64285
CVE-2026-64285 affects the Linux kernel KVM SEV SNP path. When populating a guest’s initial CPUID data, KVM may pin a source page as writable and write back data if the userspace-provided CPUID data is rejected by trusted firmware, risking clobbering read-only memory due to kernel mappings. Multi...
CVE-2026-64284
CVE-2026-64284 — Linux kernel (KVM/x86): The vulnerability involves moving the handling of fastpath userspace exits into vendor code so KVM can run vendor-specific operations before userspace gains control of the vCPU. The description notes that, for VMX (and soon SVM), KVM must flush the PML buf...
Kata Containers have VM Escape via virtiofsd Argument Injection through Default-Enabled Pod Annotations
...
PT-2026-64505
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the KVM x86 module where fastpath userspace exits may occur before the vendor's exit handler runs. This prevents KVM from executing vendor-specific operations required...
PT-2026-64503
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the KVM arm64 implementation where a race condition occurs between the kvm translate vncr function and an MMU notifier. In this scenario, an early return fails to...
Linux Distros Unpatched Vulnerability : CVE-2026-64286
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - KVM: arm64: Clear hyprunningvcpu when flushing the pKVM hyp vCPU flushhypvcpu copies the host vCPU context into the hyp's private vCPU on every run. ctxttovcpu...
CVE-2026-64247
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
CVE-2026-64247
CVE-2026-64247 concerns the Linux kernel KVM code for x86 with hyper-v virtualization. The issue arises when checking if a VP ID is in a sparse bank set: the VP ID could be copied without bounds checking, risking an out-of-bounds read when testing the sparse bank and potentially triggering an unn...
CVE-2026-64247 KVM: x86: hyper-v: Bound the bank index when querying sparse banks
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available
A flaw was found in KVM in the Linux kernel. This vulnerability occurs due to improper validation of memory management unit MMU page roots after these pages are made available. An attacker could exploit this by triggering a scenario where KVM attempts to map memory into an invalid root, causing...
kernel: KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O
A flaw was found in the Kernel-based Virtual Machine KVM for x86. This vulnerability occurs when KVM incorrectly re-checks Level 1 L1 intercepts during the completion of userspace I/O emulation for a Level 2 L2 instruction. If the L1 or host userspace modifies I/O interception settings during thi...
CVE-2026-49745
Kernel software installed and running inside a Guest VM may post improper commands to the GPU Firmware to trigger a write of data outside the Guest's virtualised GPU memory. Software installed and run under a Guest VM can send commands to the GPU which result in out of bounds memory accesses. The...
CVE-2026-49744
Kernel software installed and running inside a Guest VM may post improper commands to the GPU Firmware to trigger a write of data outside the Guest's virtualised GPU memory. Out of bounds accesses triggered by malware introduced to a Guest KMD could allow privilege escalation which escapes...
CVE-2026-49745
Kernel software installed and running inside a Guest VM may post improper commands to the GPU Firmware to trigger a write of data outside the Guest's virtualised GPU memory. Software installed and run under a Guest VM can send commands to the GPU which result in out of bounds memory accesses. The...