0.0
NA
CVE-2026-64602
iio: adc: spear: Initialize completion before requesting IRQ
Description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "spear_adc_probe() in drivers/iio/adc/spear_adc.c registers its interrupt handler with devm_request_irq() before it initializes st->completion with init_completion(). If an interrupt arrives after devm_request_irq() and before init_completion(), the handler calls complete() on an uninitialized completion, causing a kernel panic. The probe path, in spear_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, spear_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ spear_adc_isr() calls complete(): complete(&st->completion); If the device raises an interrupt before init_completion() runs, complete() acquires the uninitialized wait.lock and walks the zeroed task_list in swake_up_locked(). The zeroed task_list makes list_empty() return false, so swake_up_locked() dereferences a NULL list entry, triggering a KASAN wild-memory-access." Fix the chance of a spurious IRQ causing an uninitialized pointer dereference by moving init_completion() above devm_request_irq().

INFO

Published Date :

Aug. 6, 2026, 8:16 a.m.

Last Modified :

Aug. 6, 2026, 8:16 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64602 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Initialize completion before requesting interrupt handler in the Linux kernel.
  • Move init_completion() before devm_request_irq().
  • Rebuild and deploy the updated kernel.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64602 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64602 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64602 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64602 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 06, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': 'aea8ae6c4d3ed58d9223360f758df6bd8b90c608', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': '67a49ab41320b3f721ce4be7447754ff040acbd5', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': 'a50757398794aaa25f908b96c6733e045466cba4', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': 'f3f90bc7b38ba3ff14f131cea0f8eb77624787a8', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': '37077d8271b1f24894fbc21bca1c4cd337525d31', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': 'bbfebae473ac2c8a194523b29ccb9b45f02f134c', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': 'eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4', 'versionType': 'git'}, {'status': 'affected', 'version': 'b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed', 'lessThan': '3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0', 'versionType': 'git'}], 'programFiles': ['drivers/iio/adc/spear_adc.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.16'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.16', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc3', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/iio/adc/spear_adc.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "spear_adc_probe() in drivers/iio/adc/spear_adc.c registers its interrupt handler with devm_request_irq() before it initializes st->completion with init_completion(). If an interrupt arrives after devm_request_irq() and before init_completion(), the handler calls complete() on an uninitialized completion, causing a kernel panic. The probe path, in spear_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, spear_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ spear_adc_isr() calls complete(): complete(&st->completion); If the device raises an interrupt before init_completion() runs, complete() acquires the uninitialized wait.lock and walks the zeroed task_list in swake_up_locked(). The zeroed task_list makes list_empty() return false, so swake_up_locked() dereferences a NULL list entry, triggering a KASAN wild-memory-access." Fix the chance of a spurious IRQ causing an uninitialized pointer dereference by moving init_completion() above devm_request_irq().
    Added Reference https://git.kernel.org/stable/c/37077d8271b1f24894fbc21bca1c4cd337525d31
    Added Reference https://git.kernel.org/stable/c/3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0
    Added Reference https://git.kernel.org/stable/c/67a49ab41320b3f721ce4be7447754ff040acbd5
    Added Reference https://git.kernel.org/stable/c/a50757398794aaa25f908b96c6733e045466cba4
    Added Reference https://git.kernel.org/stable/c/aea8ae6c4d3ed58d9223360f758df6bd8b90c608
    Added Reference https://git.kernel.org/stable/c/bbfebae473ac2c8a194523b29ccb9b45f02f134c
    Added Reference https://git.kernel.org/stable/c/eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4
    Added Reference https://git.kernel.org/stable/c/f3f90bc7b38ba3ff14f131cea0f8eb77624787a8
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.