CVE-2026-64602

CVE CVE-2026-64602EUVD EUVD-2026-53788Published 2026-08-06T07:13:54.000Z

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 6.18.39; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <a50757398794aaa25f908b96c6733e045466cba4; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <f3f90bc7b38ba3ff14f131cea0f8eb77624787a8; patch: 7.1.4; patch: 6.12.96; patch: 6.6.145; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <67a49ab41320b3f721ce4be7447754ff040acbd5; patch: 0; patch: 5.15.212; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <37077d8271b1f24894fbc21bca1c4cd337525d31; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <bbfebae473ac2c8a194523b29ccb9b45f02f134c; 3.16; patch: 6.1.178; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4; patch: 7.2-rc3; b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed <aea8ae6c4d3ed58d9223360f758df6bd8b90c608; patch: 5.10.261

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.