CVE-2026-64500
iio: adc: lpc32xx: Initialize completion before requesting IRQ
Description
In the Linux kernel, the following vulnerability has been resolved: iio: adc: lpc32xx: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "lpc32xx_adc_probe() in drivers/iio/adc/lpc32xx_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 lpc32xx_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, lpc32xx_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ lpc32xx_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 :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64500
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
- Move init_completion() above devm_request_irq().
- Ensure interrupts are handled after completion initialization.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64500.
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-64500 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-64500
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-64500 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64500 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
Jul. 25, 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': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '7090c0d29708ee305022d0ea7b37612b33242fa2', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '0e33587967b356519aa6f220b5b43c6976320397', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '1ddf7b6ffb8ebb22b92a184a9eaa76277ef0c7cd', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '820c4f15353efe9a9429ae86ccceeaf4e0e4e585', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '48eccc6caed4e62c0f199ab3a3772fa969cd3b2d', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '9e2e8b8cdfd37ae7c7a8a5c96c59e98a768731c4', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': '2f18c5551aa97ca7f39dbb151c67c9053ccadc17', 'versionType': 'git'}, {'status': 'affected', 'version': '7901b2a1453e48c9defff2c97c67d3089bf4df7a', 'lessThan': 'e561b35633f450ee607e87a6401d97f156a0cd54', 'versionType': 'git'}], 'programFiles': ['drivers/iio/adc/lpc32xx_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': '4.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.12', '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/lpc32xx_adc.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: iio: adc: lpc32xx: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "lpc32xx_adc_probe() in drivers/iio/adc/lpc32xx_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 lpc32xx_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, lpc32xx_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ lpc32xx_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/0e33587967b356519aa6f220b5b43c6976320397 Added Reference https://git.kernel.org/stable/c/1ddf7b6ffb8ebb22b92a184a9eaa76277ef0c7cd Added Reference https://git.kernel.org/stable/c/2f18c5551aa97ca7f39dbb151c67c9053ccadc17 Added Reference https://git.kernel.org/stable/c/48eccc6caed4e62c0f199ab3a3772fa969cd3b2d Added Reference https://git.kernel.org/stable/c/7090c0d29708ee305022d0ea7b37612b33242fa2 Added Reference https://git.kernel.org/stable/c/820c4f15353efe9a9429ae86ccceeaf4e0e4e585 Added Reference https://git.kernel.org/stable/c/9e2e8b8cdfd37ae7c7a8a5c96c59e98a768731c4 Added Reference https://git.kernel.org/stable/c/e561b35633f450ee607e87a6401d97f156a0cd54