GHSA-QCHF-H949-MMVH
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98676"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:20Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: adc: ade9000: fix NULL pointer dereference in clkout registration\n\nade9000_setup_clkout() passes NULL as the register address when\nregistering a divider clock. During clock registration, the common\nclock framework calls clk_divider_recalc_rate(), which dereferences\nthe address through readl(). As a result, probing an ADE9000 configured\nas a clock provider with an external input clock crashes.\n\nCLKOUT passes CLKIN through without changing its rate. Register it as\na 1:1 fixed-factor clock, which does not require register access.\n\nThis change does not affect the configuration using the internal clock,\nfor which the driver does not register a clock provider.",
"id": "GHSA-qchf-h949-mmvh",
"modified": "2026-10-18T18:31:59Z",
"published": "2026-10-18T18:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98676"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/134aa31a8d4e71f6ab1d155ad7b4502508832f72"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/49ee1c6a3ebda6b7de06b2961b0e09c1c3fe536a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d2400175228fbc10b29c49a7b5f70a7e80d144dd"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.