VulnerabilityPublished 18 Oct 2026Updated 21 Oct 2026

CVE-2026-98665: Linux kernel · iio: health: max30102: fix NULL dereference in interrupt handler

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f0ea4824deebf21dacfbe397c4b0a5fd3e745a8d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f0ea4824deebf21dacfbe397c4b0a5fd3e745a8d, eeb23ba97bd8016e815ef70300b8d34a0a316b90, 60699102827fdb51f9591414165359c8e867f302 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 90579b69e94bf11ea0745ff003e82a6ce9725f96, < f0ea4824deebf21dacfbe397c4b0a5fd3e745a8d	Fixed in f0ea4824deebf21dacfbe397c4b0a5fd3e745a8d
LinuxLinux	Affected ≥ 90579b69e94bf11ea0745ff003e82a6ce9725f96, < eeb23ba97bd8016e815ef70300b8d34a0a316b90	Fixed in eeb23ba97bd8016e815ef70300b8d34a0a316b90
LinuxLinux	Affected ≥ 90579b69e94bf11ea0745ff003e82a6ce9725f96, < 60699102827fdb51f9591414165359c8e867f302	Fixed in 60699102827fdb51f9591414165359c8e867f302
LinuxLinux	Affected ≥ 90579b69e94bf11ea0745ff003e82a6ce9725f96, < 8d6f98972fe2bd6f73f39d982af0c85d766a1503	Fixed in 8d6f98972fe2bd6f73f39d982af0c85d766a1503
LinuxLinux	Affected ≥ 90579b69e94bf11ea0745ff003e82a6ce9725f96, < 2a74f30a7bb305cdc5c3e3e9239b32bb84f3529f	Fixed in 2a74f30a7bb305cdc5c3e3e9239b32bb84f3529f
LinuxLinux	Affected =4.16	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: iio: health: max30102: fix NULL dereference in interrupt handler The interrupt is requested in max30102_probe() and stays enabled for the lifetime of the device, but indio_dev->active_scan_mask is only valid while a buffer is enabled. When an interrupt arrives while no buffer is enabled, the handler dereferences the NULL active_scan_mask: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Call trace: __bitmap_weight+0x64/0x98 (P) max30102_interrupt_handler+0x48/0x160 [max30102] Call max30102_fifo_count() at the top of the handler and return early unless it reports a FIFO sample is ready. Because FIFO_RDY is the only interrupt source enabled in max30102_chip_init(), an invocation of max30102_interrupt_handler() without the FIFO_RDY interrupt status bit set carries no data to read and can return before touching active_scan_mask. A negative return from max30102_fifo_count() indicates a failed interrupt status read and is treated the same way.

References

Community reviews

Loading reviews…