---
id: "CVE-2026-98665"
kind: "vulnerability"
aliases: ["CVE-2026-98665"]
title: "Linux kernel: MAX30102 sensor interrupt can crash the system with NULL dereference"
severity: "low"
cvss: null
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["embedded", "iio-sensors", "linux-kernel", "other"]
not_affected_if: ["module-not-loaded", "no-max30102-hardware"]
published_at: "2026-10-18T16:17:19+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:19:27+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98665", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel: MAX30102 sensor interrupt can crash the system with NULL dereference

A kernel driver for the MAX30102 heart-rate sensor dereferenced a NULL pointer in its interrupt handler when no data buffer was active. The result is a kernel crash (denial of service) triggered by the sensor's interrupt line.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the `max30102` kernel module is loaded with `lsmod | grep max30102`
- Confirm the kernel version against the fixed release listed in the upstream commit: unknown

## Fix

- Update the Linux kernel to a release that includes the upstream fix in iio: health: max30102 (version unknown)
- Until patched, unload the driver with `modprobe -r max30102` if the sensor is not needed

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98665

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_