# CVE-2026-98675: iio: adc: ade9000: handle Phase C dip events in IRQ1 handler

> The ADE9000 ADC driver failed to report Phase C dip events due to an incorrect scan limit, potentially affecting power monitoring accuracy.

- **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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98675, DEBIAN-CVE-2026-98675, GHSA-qpvq-cwgm-ghf8, UBUNTU-CVE-2026-98675

## What is CVE-2026-98675?

CVE-2026-98675 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: adc: ade9000: handle Phase C dip events in IRQ1 handler

ADE9000_ST1_CROSSING_DEPTH is the exclusive upper bound for scanning the
STATUS1 event bits, so a value of 25 left out the highest event bit,
ADE9000_ST1_DIPC_BIT (bit 25). Phase C dip events were never reported.

Bump the value to 26 so bit 25 is scanned.

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


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

Apply the vendor's patch.

## Is CVE-2026-98675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98675 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-98675 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-98675/ (Markdown: https://insights.sbomify.com/CVE-2026-98675/index.md)
```

## Sources

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

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