Strix
26.1K

CVE-2026-64602

Unknown

Last modified

CVE-2026-64602 is a vulnerability of currently unknown severity. 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().

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().

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < aea8ae6c4d3ed58d9223360f758df6bd8b90c608; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < 67a49ab41320b3f721ce4be7447754ff040acbd5; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < a50757398794aaa25f908b96c6733e045466cba4; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < f3f90bc7b38ba3ff14f131cea0f8eb77624787a8; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < 37077d8271b1f24894fbc21bca1c4cd337525d31; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < bbfebae473ac2c8a194523b29ccb9b45f02f134c; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4; >= b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed, < 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0
LinuxLinux3.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-64602?
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().
How severe is CVE-2026-64602?
Severity scoring for CVE-2026-64602 is pending analysis.
How do I fix CVE-2026-64602?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-64602?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST