VulnerabilityPublished 6 Aug 2026Updated 28 Oct 2026

CVE-2026-64602: Linux kernel · iio: adc: spear: Initialize completion before requesting IRQ

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 5.15.0-1117.124~20.04.1 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 11:49 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 5.15.0-1117.124~20.04.1, 5.15.0-1123.132~20.04.1, 5.15.0-1122.131~20.04.1 +58

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-31.31	Fixed in 7.0.0-31.31
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1012.12	Fixed in 7.0.0-1012.12
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1013.13	Fixed in 7.0.0-1013.13
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1011.11	Fixed in 7.0.0-1011.11
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1006.7	Fixed in 7.0.0-1006.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and has been applied in multiple Linux kernel versions including 5.15.0-1117.124~20.04.1 and later. Users should update to these fixed kernel versions to remediate the vulnerability. No additional mitigation steps are required beyond applying the official patches.

Description

A vulnerability in the Linux kernel's spear ADC driver occurs because the completion structure is initialized after the interrupt handler is registered. If an interrupt triggers before initialization, the handler calls complete() on an uninitialized completion, causing a kernel panic due to a wild memory access. This flaw has been fixed by moving the initialization before the interrupt request. Multiple Linux kernel versions, including various linux-aws versions, are affected.

Impact

If exploited, this vulnerability can cause a kernel panic, resulting in a denial of service condition. The kernel panic arises from a wild memory access when the interrupt handler operates on an uninitialized completion structure. There is no indication of privilege escalation or code execution beyond system instability.

Summary

The Linux kernel's spear ADC driver (drivers/iio/adc/spear_adc.c) improperly registers its interrupt handler with devm_request_irq() before initializing the completion structure with init_completion(). If an interrupt arrives between these operations, the interrupt handler calls complete() on an uninitialized completion, leading to a kernel panic caused by a KASAN wild-memory-access. The fix involves moving the init_completion() call before devm_request_irq() to ensure the completion is properly initialized before any interrupts can trigger the handler.

GCVE source: db.gcve.eu
OSV ID: UBUNTU-CVE-2026-64602
Osv Schema Version: 1.7.0
Ecosystems: Ubuntu:Pro:14.04:LTS, Ubuntu:Pro:16.04:LTS, Ubuntu:16.04:LTS, Ubuntu:Pro:FIPS-updates:16.04:LTS, Ubuntu:Pro:FIPS:16.04:LTS, Ubuntu:Pro:18.04:LTS, Ubuntu:18.04:LTS, Ubuntu:Pro:FIPS-updates:18.04:LTS, Ubuntu:Pro:FIPS:18.04:LTS, Ubuntu:Pro:20.04:LTS, Ubuntu:20.04:LTS, Ubuntu:Pro:FIPS-updates:20.04:LTS, Ubuntu:Pro:FIPS:20.04:LTS, Ubuntu:22.04:LTS, Ubuntu:Nvidia-BlueField:22.04:LTS, Ubuntu:Pro:Realtime:22.04:LTS, Ubuntu:Pro:FIPS-preview:22.04:LTS, Ubuntu:Pro:FIPS-updates:22.04:LTS, Ubuntu:24.04:LTS, Ubuntu:Nvidia-BlueField:24.04:LTS, Ubuntu:Pro:Realtime:24.04:LTS, Ubuntu:Pro:FIPS-updates:24.04:LTS, Ubuntu:26.04:LTS

References

Community reviews

Loading reviews…