Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64602iio: 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().

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 11 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < aea8ae6c4d3ed58d9223360f758df6bd8b90c608
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < 67a49ab41320b3f721ce4be7447754ff040acbd5
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < a50757398794aaa25f908b96c6733e045466cba4
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < f3f90bc7b38ba3ff14f131cea0f8eb77624787a8
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < 37077d8271b1f24894fbc21bca1c4cd337525d31
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < bbfebae473ac2c8a194523b29ccb9b45f02f134c
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4
    • affected b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed – < 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64602 badge
[![CVE-2026-64602](https://cveledger.app/badge/CVE-2026-64602.svg)](https://cveledger.app/cve/CVE-2026-64602)

Record last updated .