CVE-2026-89939

In the Linux kernel 's iio: chemical: atlas-sensor driver, atlas_buffer_postenable() acquires a runtime PM reference via pm_runtime_resume_and_get() but returns the result of atlas_set_interrupt() directly. If that call fails, the reference is leaked , preventing the device from ever autosuspendi...

CVE-2026-89937

CVE-2026-89937 affects the Linux kernel 's IIO chemical sensor driver sgp30 . The root cause is that sgp_probe() fails to check the return value of kthread_run() when creating the IAQ (Indoor Air Quality) thread. If the thread creation fails, an error pointer is stored but the probe still returns...

CVE-2026-89936

CVE-2026-89936 affects the Linux kernel 's iio: dac: m62332 driver (Microchip M62332 DAC). The function m62332_set_value() enables the Vcc regulator on every non-zero channel write and disables it on every zero write, but does not track the channel's prior state. Because the regulator is referenc...

CVE-2026-89935

CVE-2026-89935 affects the Linux kernel iio: light: apds9306 driver (APDS9306 ambient light sensor). The root cause is a runtime PM reference leak : apds9306_read_data() calls pm_runtime_resume_and_get() but several error paths return without the matching pm_runtime_put_autosuspend(), preventing ...

CVE-2026-89934

CVE-2026-89934 is a runtime PM (Power Management) reference leak in the Linux kernel's LTRF216A light sensor driver (IIO subsystem). The function ltrf216a_get_lux() acquires a runtime PM reference via ltrf216a_set_power_state(data, true), but when ltrf216a_read_data() fails, it returns without re...

CVE-2026-89933

CVE-2026-89933 is a NULL pointer dereference in the Linux kernel's IIO pressure driver for the DPS310 (Infineon IFX3100). When the device is enumerated via its ACPI HID (IFX3100) , i2c_client_get_device_id() returns NULL because the ACPI-derived client name does not match the driver's i2c_device_...

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

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

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

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

CVE-2026-89927

CVE-2026-89927 is an integer overflow vulnerability in the Linux kernel's KVM x86 Hyper-V synthetic timer (stimer) emulation. When the STIMER COUNT MSR is programmed with a value close to U64_MAX , the deadline calculation overflows, producing a deadline in the past. This causes the hrtimer to fi...

CVE-2026-89926

CVE-2026-89926 affects the Linux kernel KVM s390 subsystem in the __import_wp_info() function. The root cause is a type truncation : the user-space-controlled kvm_hw_breakpoint::len (a __u64) is assigned to wp_info->len (an int). The bounds check evaluates the truncated value, but the subseque...

CVE-2026-89925

CVE-2026-89925 affects the Linux kernel KVM s390 module. The root cause is a memory leak in the guest debug handling path: bp_data is freed via kfree() only in the error case of KVM_SET_GUEST_DEBUG, so every successful KVM_SET_GUEST_DEBUG call leaks the allocation. The practical impact is a per-c...

CVE-2026-89924

This Linux kernel vulnerability affects the KVM s390 subsystem's guest debug interface. In __import_wp_info(), per-watchpoint old_data buffers are allocated to back up original guest memory contents. When a later watchpoint in the same KVM_SET_GUEST_DEBUG request fails to import, kvm_s390_import_...

CVE-2026-89922

CVE-2026-89922 is a race condition in the Linux kernel's KVM s390 subsystem. The function __import_wp_info() uses kvm_read_guest() to back up guest memory contents of a watchpoint, which resolves memslots via __kvm_memslots(). This call requires holding kvm->srcu (or kvm->slots_lock), but t...

CVE-2026-89923

This is a memory leak in the Linux kernel's KVM s390 module. When a vCPU is destroyed while hardware breakpoints remain armed (the normal case when a VMM exits or crashes), hw_bp_info, hw_wp_info, and old_data buffers are leaked because kvm_s390_clear_bp_data() is only invoked from the guest-debu...

CVE-2026-89921

CVE-2026-89921 affects the Linux kernel KVM s390 architecture. The function __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq, but the full ext substructure is copied into the CPU local variable on injection, leaving ext_params and pad with sta...

CVE-2026-89920

CVE-2026-89920 affects the Linux kernel's KVM s390 subsystem. The vulnerability arises when channel-subsystem damage (CK) machine checks are unnecessarily reinjected into a guest VM, even though the guest channel subsystem is emulated in the userspace VMM. This reinjection causes a kfree of a sta...

CVE-2026-89919

CVE-2026-89919 affects the Linux kernel's KVM s390 subsystem. The keyop function reads kvm->arch.gmap->asce without holding the mmu_lock read-side, unlike every other dat_* consumer in the same file. Because gmap->asce is mutated under write_lock(mmu_lock) by gmap_set_limit(), a concurre...