Live › vulnerability › CVE-2026-98676
Go to dashboardA Linux kernel IIO driver for the ADE9000 energy-measurement chip passes a NULL register address when registering a clock divider, so probing the device as a clock provider with an external input clock dereferences NULL and crashes. The sources describe a kernel crash (denial of service) during driver probe, not code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems running a Linux kernel with the ADE9000 IIO driver that configure the chip as a clock provider using an external input clock. The sources say the internal-clock configuration is not affected because the driver does not register a clock provider there. Teams not using the ADE9000 chip can skip it.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98676")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.