103851 matches found
CVE-2026-98676
In the Linux kernel, the following vulnerability has been resolved: iio: adc: ade9000: fix NULL pointer dereference in clkout registration ade9000setupclkout passes NULL as the register address when registering a divider clock. During clock registration, the common clock framework calls...
CVE-2026-98665 iio: health: max30102: fix NULL dereference in interrupt handler
In the Linux kernel, the following vulnerability has been resolved: iio: health: max30102: fix NULL dereference in interrupt handler The interrupt is requested in max30102probe and stays enabled for the lifetime of the device, but indiodev-activescanmask is only valid while a buffer is enabled...
CVE-2026-98665
In the Linux kernel, the following vulnerability has been resolved: iio: health: max30102: fix NULL dereference in interrupt handler The interrupt is requested in max30102probe and stays enabled for the lifetime of the device, but indiodev-activescanmask is only valid while a buffer is enabled...
CVE-2026-98665
The Linux kernel contains a NULL pointer dereference vulnerability within the iio: health: max30102 driver. The issue exists in the max30102_interrupt_handler because the indio_dev->active_scan_mask is only valid when a buffer is enabled, but the interrupt remains active for the device's lifet...
EUVD-2026-103919
In the Linux kernel, the following vulnerability has been resolved: iio: health: max30102: fix NULL dereference in interrupt handler The interrupt is requested in max30102probe and stays enabled for the lifetime of the device, but indiodev-activescanmask is only valid while a buffer is enabled...
CVE-2026-98665 iio: health: max30102: fix NULL dereference in interrupt handler
In the Linux kernel, the following vulnerability has been resolved: iio: health: max30102: fix NULL dereference in interrupt handler The interrupt is requested in max30102probe and stays enabled for the lifetime of the device, but indiodev-activescanmask is only valid while a buffer is enabled...
CVE-2026-98651 KVM: s390: Properly handle NULL pointer in dat_cond_set_storage_key()
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Properly handle NULL pointer in datcondsetstoragekey Some callers pass NULL as oldkey. Calling pagecondsetstoragekey will cause that NULL pointer to get dereferenced. Fix by checking for NULL and assigning the pointer ...
EUVD-2026-103565
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Properly handle NULL pointer in datcondsetstoragekey Some callers pass NULL as oldkey. Calling pagecondsetstoragekey will cause that NULL pointer to get dereferenced. Fix by checking for NULL and assigning the pointer ...
CVE-2026-98651
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Properly handle NULL pointer in datcondsetstoragekey Some callers pass NULL as oldkey. Calling pagecondsetstoragekey will cause that NULL pointer to get dereferenced. Fix by checking for NULL and assigning the pointer ...
CVE-2026-98651
The Linux kernel contains a vulnerability in the KVM s390 component where the function page_cond_set_storage_key() improperly handles a NULL pointer passed as oldkey by certain callers. This improper handling leads to a NULL pointer dereference , which can cause system crashes. The issue is resol...
CVE-2026-98651 KVM: s390: Properly handle NULL pointer in dat_cond_set_storage_key()
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Properly handle NULL pointer in datcondsetstoragekey Some callers pass NULL as oldkey. Calling pagecondsetstoragekey will cause that NULL pointer to get dereferenced. Fix by checking for NULL and assigning the pointer ...
EUVD-2026-103551
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Do not clear VM-wide SVE feature on vCPU init failure pkvmvcpuinitsve clears KVMARMVCPUSVE in kvm-arch.vcpufeatures when it fails, but vcpuhassve tests KVMARCHFLAGGUESTHASSVE, which is left set. Later vCPUs on that VM...
CVE-2026-98637
The Linux kernel contains a vulnerability in the KVM subsystem for arm64 architecture. During vCPU initialization , the function pkvm_vcpu_init_sve() incorrectly clears KVM_ARM_VCPU_SVE in kvm->arch.vcpu_features upon failure, while leaving KVM_ARCH_FLAG_GUEST_HAS_SVE set. This causes subseque...
CVE-2026-98637 KVM: arm64: Do not clear VM-wide SVE feature on vCPU init failure
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Do not clear VM-wide SVE feature on vCPU init failure pkvmvcpuinitsve clears KVMARMVCPUSVE in kvm-arch.vcpufeatures when it fails, but vcpuhassve tests KVMARCHFLAGGUESTHASSVE, which is left set. Later vCPUs on that VM...
CVE-2026-98637 KVM: arm64: Do not clear VM-wide SVE feature on vCPU init failure
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Do not clear VM-wide SVE feature on vCPU init failure pkvmvcpuinitsve clears KVMARMVCPUSVE in kvm-arch.vcpufeatures when it fails, but vcpuhassve tests KVMARCHFLAGGUESTHASSVE, which is left set. Later vCPUs on that VM...
CVE-2026-98618
The Linux kernel contains a vulnerability in the fbnic driver related to standalone channels. The issue arises because the driver's allocation path excludes FBNIC_MAX_TXQS from the layout. In a 64-Tx/64-Rx configuration, the system records 128 vectors but only allocates 64, resulting in NULL entr...
EUVD-2026-103663
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: Handle maximum standalone channels Standalone channels use one NAPI vector for each Tx and Rx queue. fbnic's allocation path excludes FBNICMAXTXQS from that layout. A 64-Tx/64-Rx configuration therefore records 128...
CVE-2026-98618 eth: fbnic: Handle maximum standalone channels
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: Handle maximum standalone channels Standalone channels use one NAPI vector for each Tx and Rx queue. fbnic's allocation path excludes FBNICMAXTXQS from that layout. A 64-Tx/64-Rx configuration therefore records 128...
CVE-2026-98618 eth: fbnic: Handle maximum standalone channels
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: Handle maximum standalone channels Standalone channels use one NAPI vector for each Tx and Rx queue. fbnic's allocation path excludes FBNICMAXTXQS from that layout. A 64-Tx/64-Rx configuration therefore records 128...
CVE-2026-98616 eth: fbnic: reset num_napi when the napi vectors are freed
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: reset numnapi when the napi vectors are freed fbn-numnapi is the count of live napi vectors, each of which owns an IRQ. The PM path had freed them without clearing the count. fbnicpmsuspend tears the datapath down via...