Lucene search
+L

386 matches found

NVD
NVD
added 4 hours ago2 views

CVE-2026-74517

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs Cancel and flush the I/O APIC's delayed EOI handling work during the "pre VM destroy" phase, before vCPUs are destroyed, as processing the EOI broadcast will...

SaveExploits0References2
Cvelist
Cvelist
added 5 hours ago3 views

CVE-2026-74517 KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs Cancel and flush the I/O APIC's delayed EOI handling work during the "pre VM destroy" phase, before vCPUs are destroyed, as processing the EOI broadcast will...

SaveExploits0References2
EUVD
EUVD
added 5 hours ago2 views

EUVD-2026-59710

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs Cancel and flush the I/O APIC's delayed EOI handling work during the "pre VM destroy" phase, before vCPUs are destroyed, as processing the EOI broadcast will...

5.5AI score
SaveExploits0References2
NVD
NVD
added 11 hours ago3 views

CVE-2026-72284

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs Ignore KVM's internal "service pending PV EOI" request if the vCPU has disabled PV EOIs since the request was made. Asserting that PV EOIs are enabled can fai...

SaveExploits0References6
Positive Technologies
Positive Technologies
added 18 hours ago6 views

PT-2026-72969

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs Cancel and flush the I/O APIC's delayed EOI handling work during the "pre VM destroy" phase, before vCPUs are destroyed, as processing the EOI broadcast will...

5.4AI score
SaveExploits0References3
RedhatCVE
RedhatCVE
added 4 days ago6 views

CVE-2026-68093

A flaw was found in the Linux kernel's KVM Kernel-based Virtual Machine. When a virtual CPU vCPU is scheduled out and its physical CPU pCPU undergoes a hotplug cycle offline and then online, the vCPU might resume with an Address Space Identifier ASID that has been reassigned to another vCPU from ...

7CVSS5.1AI score0.0018EPSS
SaveExploits0References4
OSV
OSV
added 5 days ago2 views

UBUNTU-CVE-2026-68093

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Bump asidgeneration on CPU online to avoid ASID collision after hotplug If a vCPU stays scheduled out or blocked while the last pCPU it ran on goes through a hotplug cycle online-offline-online, and the vCPU then resume...

5.5AI score0.0018EPSS
SaveExploits0References7
AstraLinux
AstraLinux
added 5 days ago10 views

Astra Linux – Vulnerability in Linux 6.12

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ignore -EBUSY when checking nested events from vcpublock Ignore -EBUSY when checking nested events after exiting a blocking state. This applies when L2 is active; exiting to userspace will typically result in a spurious...

5.5CVSS4.6AI score0.00119EPSS
SaveExploits0References2
Tenable Nessus
Tenable Nessus
added 5 days ago5 views

Linux Distros Unpatched Vulnerability : CVE-2026-68093

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - KVM: SVM: Bump asidgeneration on CPU online to avoid ASID collision after hotplug If a vCPU stays scheduled out or blocked while the last pCPU it ran on goes...

5.6AI score0.0018EPSS
SaveExploits0References4
ATTACKERKB
ATTACKERKB
added 2026/08/06 7:13 a.m.10 views

CVE-2026-64604

In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode When updating CR8 intercepts, get vmcs12 if and only if the vCPU is in guest mode so that a future change can have update CR8 intercepts during vCPU...

5.3AI score0.00164EPSS
SaveExploits0References9Affected Software1
UbuntuCve
UbuntuCve
added 2026/08/06 12:0 a.m.3 views

CVE-2026-64604

In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode When updating CR8 intercepts, get vmcs12 if and only if the vCPU is in guest mode so that a future change can have update CR8 intercepts during vCPU...

5.4AI score0.00164EPSS
SaveExploits0References10
CVE
CVE
added 2026/08/04 6:23 a.m.93 views

CVE-2026-64562

CVE-2026-64562 : In the Linux kernel KVM nVMX, a shadow VMCS could be freed prematurely by free_nested() while vmcs01 still referenced it. Since this occurs asynchronously with respect to loaded_vmcs_clear(), a vCPU could migrate and __loaded_vmcs_clear() may then execute VMCLEAR. The vulnerabili...

8.8CVSS5.5AI score0.0012EPSS
SaveExploits0References5
Cvelist
Cvelist
added 2026/08/04 6:23 a.m.50 views

CVE-2026-64562 KVM: nVMX: Hide shadow VMCS right after VMCLEAR

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Hide shadow VMCS right after VMCLEAR freenested frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loadedvmcsclear, the vCPU might migrate before the pointer is cleare...

8.8CVSS0.0012EPSS
SaveExploits0References5
Positive Technologies
Positive Technologies
added 2026/08/04 12:0 a.m.28 views

PT-2026-67669

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Hide shadow VMCS right after VMCLEAR free nested frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loaded vmcs clear, the vCPU might migrate before the pointer is...

5.5AI score0.0012EPSS
SaveExploits0References6
SUSE CVE
SUSE CVE
added 2026/07/25 4:46 p.m.6 views

SUSE 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...

8.2CVSS5.7AI score0.0017EPSS
SaveExploits0References3
NVD
NVD
added 2026/07/25 10:17 a.m.6 views

CVE-2026-64286

In the Linux kernel, the following vulnerability has been resolved: 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 expects a guest context to have a NULL hyprunningvcpu, which is only...

8.2CVSS0.0017EPSS
SaveExploits0References5
NVD
NVD
added 2026/07/25 10:17 a.m.7 views

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

8.2CVSS0.0017EPSS
SaveExploits0References5
UbuntuCve
UbuntuCve
added 2026/07/25 10:17 a.m.12 views

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

8.2CVSS5.4AI score0.0017EPSS
SaveExploits0References7
Cvelist
Cvelist
added 2026/07/25 9:14 a.m.49 views

CVE-2026-64516 drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access...

8.8CVSS0.00112EPSS
SaveExploits0References2
CVE
CVE
added 2026/07/25 9:14 a.m.53 views

CVE-2026-64516

The CVE-2026-64516 issue affects the Linux kernel’s DRM/AMDGPU VCE1 path. Root cause: the VCPU BO size did not account for the actual firmware offset, risking out-of-bounds access; fixes include subtracting the firmware offset from the firmware size, aligning stack and data offsets to the 32K TLB...

8.8CVSS5.8AI score0.00112EPSS
SaveExploits0References2
Rows per page
Query Builder