AZL-101690 CVE-2026-89811 affecting package kernel 6.6.157.1-1

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES Micro Engine Scheduler does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race conditio...

DEBIAN-CVE-2026-89811

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES Micro Engine Scheduler does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race conditio...

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

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

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

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

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

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

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

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

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

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

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

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

EUVD-2026-80518

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start an...

CVE-2026-89917 KVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle VNCR TLB invalidation race with vcpuput VNCR unmapping While VNCR TLB invalidation always occurs under the MMU lock, vcpuput doesn't, while it unmaps the VNCR page. The problem is that the invalidation evaluate...

CVE-2026-89916 KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the...

CVE-2026-89915 KVM: arm64: Remove VM-wide VNCR mapping counter

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Remove VM-wide VNCR mapping counter The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when...

EUVD-2026-80515

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Remove VM-wide VNCR mapping counter The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when...

CVE-2026-89915

This vulnerability affects the Linux kernel's KVM arm64 subsystem, where a flawed VM-wide VNCR mapping counter is used to decide whether an L1-provided VNCR page is mapped in L0 during TLB invalidation. The counter can result in missed TLB invalidations , and fails when an L1 vCPU invalidates its...