Lucene search
+L

103881 matches found

osv_cve
osv_cve
•added 2026/10/18 3:45 p.m.•6 views

CVE-2026-98676 iio: adc: ade9000: fix NULL pointer dereference in clkout registration

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

5.7AI score
SaveExploits0References6
Cvelist
Cvelist
•added 2026/10/18 3:45 p.m.•30 views

CVE-2026-98676 iio: adc: ade9000: fix NULL pointer dereference in clkout registration

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

0.00198EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/10/18 3:45 p.m.•9 views

EUVD-2026-103930

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

5.6AI score0.00198EPSS
SaveExploits0References3
Debian CVE
Debian CVE
•added 2026/10/18 3:44 p.m.•4 views

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

6AI score0.00168EPSS
SaveExploits0
osv_cve
osv_cve
•added 2026/10/18 3:44 p.m.•7 views

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

5.9AI score
SaveExploits0References8
EUVD
EUVD
•added 2026/10/18 3:44 p.m.•6 views

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

5.8AI score0.00168EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/18 3:44 p.m.•34 views

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

0.00168EPSS
SaveExploits0References5
CVE
CVE
•added 2026/10/18 3:44 p.m.•14 views

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

5.7AI score0.00168EPSS
SaveExploits0References5
Debian CVE
Debian CVE
•added 2026/10/18 3:20 p.m.•8 views

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

5.9AI score0.00155EPSS
SaveExploits0
osv_cve
osv_cve
•added 2026/10/18 3:20 p.m.•7 views

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

5.8AI score
SaveExploits0References5
EUVD
EUVD
•added 2026/10/18 3:20 p.m.•11 views

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

5.7AI score0.00155EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/18 3:20 p.m.•33 views

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

0.00155EPSS
SaveExploits0References2
CVE
CVE
•added 2026/10/18 3:20 p.m.•16 views

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

5.7AI score0.00155EPSS
SaveExploits0References2
EUVD
EUVD
•added 2026/10/18 3:20 p.m.•11 views

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

5.8AI score0.00166EPSS
SaveExploits0References3
osv_cve
osv_cve
•added 2026/10/18 3:20 p.m.•6 views

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

5.9AI score
SaveExploits0References6
Cvelist
Cvelist
•added 2026/10/18 3:20 p.m.•38 views

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

0.00166EPSS
SaveExploits0References3
CVE
CVE
•added 2026/10/18 3:20 p.m.•18 views

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

5.8AI score0.00166EPSS
SaveExploits0References3
CVE
CVE
•added 2026/10/18 3:19 p.m.•14 views

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

5.8AI score0.002EPSS
SaveExploits0References4
EUVD
EUVD
•added 2026/10/18 3:19 p.m.•7 views

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

5.8AI score0.002EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/18 3:19 p.m.•33 views

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

0.002EPSS
SaveExploits0References4
Rows per page
Query Builder