Lucene search
+L

9621 matches found

Cvelist
Cvelist
added 2026/09/16 10:32 a.m.13 views

CVE-2026-89959 s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix control domain removal in vfioapmdevcfgremove The vfioapconfigremove function uses the bitmapandnot function to clear bits from the matrixmdev-matrix.adm bitmap specifies the control domains assigned to the mdev...

8.8CVSS
SaveExploits0References6
CVE
CVE
added 2026/09/16 10:32 a.m.11 views

CVE-2026-89958

This vulnerability affects the Linux kernel 's s390/vfio-ap driver. The root cause is a NULL pointer dereference : the vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete callback functions acquire the matrix_mdev->kvm->lock mutex without first checking whether matrix_mdev->kvm is NULL. ...

5.6AI score
SaveExploits0References5
OSV
OSV
added 2026/09/16 10:32 a.m.1 views

CVE-2026-89959 s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix control domain removal in vfioapmdevcfgremove The vfioapconfigremove function uses the bitmapandnot function to clear bits from the matrixmdev-matrix.adm bitmap specifies the control domains assigned to the mdev...

8.8CVSS
SaveExploits0References9
EUVD
EUVD
added 2026/09/16 10:32 a.m.4 views

EUVD-2026-80558

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix dereference matrixmdev-kvm without checking for NULL The apdriver structure has two fields which are function pointers to callbacks: .onconfigchanged: called at the start of the AP bus scan function to notify th...

5.6AI score
SaveExploits0References5
EUVD
EUVD
added 2026/09/16 10:32 a.m.3 views

EUVD-2026-80531

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Ensure KVMREQGETNESTEDSTATEPAGES is cleared on VM-Exit Always check and clear KVMREQGETNESTEDSTATEPAGES when emulating a nested VM-Exit to ensure the request is cleared, even when KVM was built with CONFIGKVMHYPERV=n, ...

5.8AI score
SaveExploits0References4
Cvelist
Cvelist
added 2026/09/16 10:32 a.m.11 views

CVE-2026-89932 KVM: nVMX: Always flush vpid02 on first use

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting lastvpid=0 when allocating vpid02. nestedvmxtransitiontlbflush will always detect a VPID change on first VM-Enter after VMXON,...

8.8CVSS
SaveExploits0References7
CVE
CVE
added 2026/09/16 10:32 a.m.9 views

CVE-2026-89932

CVE-2026-89932 affects the Linux kernel's KVM nested VMX (nVMX) subsystem. The root cause is that the last_vpid variable is not reset to 0 when the L2 VPID (vpid02) is freed on VMXOFF. If KVM subsequently reuses a VPID that still has stale TLB entries on the physical CPU from a previous vCPU or a...

8.8CVSS5.8AI score
SaveExploits0References7
CVE
CVE
added 2026/09/16 10:32 a.m.8 views

CVE-2026-89931

CVE-2026-89931 affects the Linux kernel's KVM nVMX (nested virtualization) subsystem. The root cause is that the KVM_REQ_GET_NESTED_STATE_PAGES flag is not reliably cleared when emulating a nested VM-Exit, specifically when KVM is built with CONFIG_KVM_HYPERV=n . Because KVM implicitly relies on ...

5.8AI score
SaveExploits0References4
EUVD
EUVD
added 2026/09/16 10:32 a.m.4 views

EUVD-2026-80532

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting lastvpid=0 when allocating vpid02. nestedvmxtransitiontlbflush will always detect a VPID change on first VM-Enter after VMXON,...

8.8CVSS5.8AI score
SaveExploits0References7
Cvelist
Cvelist
added 2026/09/16 10:32 a.m.15 views

CVE-2026-89930 KVM: nVMX: Service local TLB flushes on failed nested VM-Enter

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits through nestedvmxvmexit, but not if a nested VM-Enter fails e.g. due to failed VMCS checks in...

9.3CVSS
SaveExploits0References7
CVE
CVE
added 2026/09/16 10:32 a.m.7 views

CVE-2026-89930

CVE-2026-89930 affects the Linux kernel's KVM nVMX subsystem (nested virtualization). The root cause is that KVM failed to service local TLB flushes when a nested VM-Enter failed (e.g., due to failed VMCS checks in nested_vmx_enter_non_root_mode()). Specifically, a failed VM-Enter would update la...

9.3CVSS5.8AI score
SaveExploits0References7
EUVD
EUVD
added 2026/09/16 10:32 a.m.4 views

EUVD-2026-80530

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits through nestedvmxvmexit, but not if a nested VM-Enter fails e.g. due to failed VMCS checks in...

9.3CVSS5.8AI score
SaveExploits0References7
EUVD
EUVD
added 2026/09/16 10:32 a.m.6 views

EUVD-2026-80528

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk kvmrmaplock deliberately elides the rmap lock when it observes an empty rmap. In that case kvmrmaplockreadonly also re-enables preemption and returns zero, so...

8.8CVSS6AI score
SaveExploits0References3
EUVD
EUVD
added 2026/09/16 10:32 a.m.4 views

EUVD-2026-80529

In the Linux kernel, the following vulnerability has been resolved: KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU When emulating INVVPID, KVM executes INVVPID on the physical CPU using vpid02 instead of the L1 assigned VPID, after doing some validations on the operands. However...

8.8CVSS5.8AI score
SaveExploits0References4
Cvelist
Cvelist
added 2026/09/16 10:32 a.m.13 views

CVE-2026-89929 KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU

In the Linux kernel, the following vulnerability has been resolved: KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU When emulating INVVPID, KVM executes INVVPID on the physical CPU using vpid02 instead of the L1 assigned VPID, after doing some validations on the operands. However...

8.8CVSS
SaveExploits0References4
OSV
OSV
added 2026/09/16 10:32 a.m.1 views

CVE-2026-89928 KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk kvmrmaplock deliberately elides the rmap lock when it observes an empty rmap. In that case kvmrmaplockreadonly also re-enables preemption and returns zero, so...

8.8CVSS
SaveExploits0References6
CVE
CVE
added 2026/09/16 10:32 a.m.9 views

CVE-2026-89929

CVE-2026-89929 affects the Linux kernel KVM subsystem, specifically the nested virtualization (nVM ) code path that emulates the INVVPID instruction. When a guest L1 vCPU migrates between physical CPUs and issues INVVPID, KVM executes the instruction on the current physical CPU rather than the on...

8.8CVSS5.8AI score
SaveExploits0References4
CVE
CVE
added 2026/09/16 10:32 a.m.15 views

CVE-2026-89928

CVE-2026-89928 is a slab use-after-free in the Linux kernel's KVM x86/mmu subsystem. The root cause is a race condition in the lockless reverse-mapping (rmap) walk: kvm_rmap_age_gfn_range() ignores the value returned by kvm_rmap_lock_readonly() and instead re-reads the rmap head via rmap_get_firs...

8.8CVSS6AI score
SaveExploits0References3
Cvelist
Cvelist
added 2026/09/16 10:32 a.m.13 views

CVE-2026-89928 KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk kvmrmaplock deliberately elides the rmap lock when it observes an empty rmap. In that case kvmrmaplockreadonly also re-enables preemption and returns zero, so...

8.8CVSS
SaveExploits0References3
EUVD
EUVD
added 2026/09/16 10:32 a.m.5 views

EUVD-2026-80526

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix length check importwpinfo struct kvmhwbreakpoint::len is a u64 that is fully controlled by user space. This is then assigned to wpinfo-len, which is an int. The bounds check is done on the truncated value while the...

5.8AI score
SaveExploits0References7
Rows per page
Query Builder