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

> A NULL pointer dereference in the ADE9000 ADC driver causes a kernel crash when probing with specific clock configurations, leading to denial of service.

- **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-98676, DEBIAN-CVE-2026-98676, GHSA-qchf-h949-mmvh, UBUNTU-CVE-2026-98676

## What is CVE-2026-98676?

CVE-2026-98676 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: fix NULL pointer dereference in clkout registration

ade9000_setup_clkout() passes NULL as the register address when
registering a divider clock. During clock registration, the common
clock framework calls clk_divider_recalc_rate(), which dereferences
the address through readl(). As a result, probing an ADE9000 configured
as a clock provider with an external input clock crashes.

CLKOUT passes CLKIN through without changing its rate. Register it as
a 1:1 fixed-factor clock, which does not require register access.

This change does not affect the configuration using the internal clock,
for which the driver does not register a clock provider.

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


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

Apply the vendor's patch.

## Is CVE-2026-98676 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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