CVE-2026-64602: iio: adc: spear: Initialize completion before requesting IRQ
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 37077d8271b1f24894fbc21bca1c4cd337525d31, 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0, 67a49ab41320b3f721ce4be7447754ff040acbd5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 37077d8271b1f24894fbc21bca1c4cd337525d31, 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0, 67a49ab41320b3f721ce4be7447754ff040acbd5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Aug 6, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.16affected
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before aea8ae6c4d3ed58d9223360f758df6bd8b90c608affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before 67a49ab41320b3f721ce4be7447754ff040acbd5affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before a50757398794aaa25f908b96c6733e045466cba4affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before f3f90bc7b38ba3ff14f131cea0f8eb77624787a8affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before 37077d8271b1f24894fbc21bca1c4cd337525d31affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before bbfebae473ac2c8a194523b29ccb9b45f02f134caffected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4affected · git
- b586e5d9eee038b8ee6f846cdb6cf2fcbcb2f4ed and later · before 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0affected · git
- before 3.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64596Aug 6, 2026 · libfs: set SB_I_NOEXEC and SB_I_NODEV by default in init_pseudo()0Monitor
- ← EarlierCVE-2026-64601Aug 6, 2026 · ALSA: us144mkii: capture_urb_complete: redundant usb_anchor_urb corrupts anchor list on each resubmission31Monitor
- Later →CVE-2026-64603Aug 6, 2026 · platform/x86: intel-hid: Protect ACPI notify handler against recursion0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 37077d8271b1f24894fbc21bca1c4cd337525d31 | Vendor (CNA) |
| Linux Linux | 3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0 | Vendor (CNA) |
| Linux Linux | 67a49ab41320b3f721ce4be7447754ff040acbd5 | Vendor (CNA) |
| Linux Linux | a50757398794aaa25f908b96c6733e045466cba4 | Vendor (CNA) |
| Linux Linux | aea8ae6c4d3ed58d9223360f758df6bd8b90c608 | Vendor (CNA) |
| Linux Linux | bbfebae473ac2c8a194523b29ccb9b45f02f134c | Vendor (CNA) |
| Linux Linux | eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4 | Vendor (CNA) |
| Linux Linux | f3f90bc7b38ba3ff14f131cea0f8eb77624787a8 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0780 · Aug 7, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0
- git.kernel.org/stable/c/67a49ab41320b3f721ce4be7447754ff040acbd5
- git.kernel.org/stable/c/a50757398794aaa25f908b96c6733e045466cba4
- git.kernel.org/stable/c/aea8ae6c4d3ed58d9223360f758df6bd8b90c608
- git.kernel.org/stable/c/bbfebae473ac2c8a194523b29ccb9b45f02f134c
- git.kernel.org/stable/c/eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4
- git.kernel.org/stable/c/f3f90bc7b38ba3ff14f131cea0f8eb77624787a8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.