# CVE-2026-98665: iio: health: max30102: fix NULL dereference in interrupt handler

> A NULL pointer dereference in the Linux kernel max30102 driver can cause a system crash when an interrupt occurs without an active buffer.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108957, BELL-CVE-2026-98665, DEBIAN-CVE-2026-98665, GHSA-g7xj-pf5g-99j9, UBUNTU-CVE-2026-98665

## What is CVE-2026-98665?

CVE-2026-98665 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-98665?


## How do I fix CVE-2026-98665?

Apply the vendor's patch.

## Is CVE-2026-98665 being exploited?

There is no known exploitation of CVE-2026-98665 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98665 and fix it if it is affected.

What it is: CVE-2026-98665 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98665 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98665/ (Markdown: https://insights.sbomify.com/CVE-2026-98665/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98665
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98665
- OSV: https://osv.dev/vulnerability/CVE-2026-98665

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98665/
Summaries are generated and may contain mistakes; the official description above is the record.