In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from… (CVE-2026-64602)
A vulnerability in the Linux kernel's spear ADC driver was resolved by correcting the initialization order of a completion object before requesting an interrupt. The issue could cause a kernel panic due to a race condition where an interrupt triggers a handler that calls complete() on an uninitialized completion, leading to a kernel memory access error.
AI Analysis
Technical Summary
The Linux kernel's spear ADC driver (drivers/iio/adc/spear_adc.c) had a flaw where the completion object 'st->completion' was initialized after registering the interrupt handler with devm_request_irq(). If an interrupt occurred before init_completion() was called, the interrupt service routine spear_adc_isr() would call complete() on an uninitialized completion structure. This caused the kernel to dereference a NULL pointer and triggered a Kernel Address Sanitizer (KASAN) wild-memory-access error, potentially leading to a kernel panic. The fix involved moving the init_completion() call to before devm_request_irq() to ensure the completion is properly initialized before any interrupts can occur.
Potential Impact
This vulnerability could cause a kernel panic due to a race condition in the interrupt handling of the spear ADC driver. The kernel panic results from dereferencing an uninitialized completion object, which may lead to denial of service on affected systems. There is no indication of privilege escalation or arbitrary code execution from the provided data.
Mitigation Recommendations
A fix is available that moves the initialization of the completion object before the interrupt request registration to prevent the race condition. Users should update their Linux kernel to a version that includes this fix. Since no vendor advisory or patch links are provided, check the official Linux kernel repositories or distributions for the patched version. Patch status is not yet confirmed in the provided data — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the report from… (CVE-2026-64602)
Description
A vulnerability in the Linux kernel's spear ADC driver was resolved by correcting the initialization order of a completion object before requesting an interrupt. The issue could cause a kernel panic due to a race condition where an interrupt triggers a handler that calls complete() on an uninitialized completion, leading to a kernel memory access error.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's spear ADC driver (drivers/iio/adc/spear_adc.c) had a flaw where the completion object 'st->completion' was initialized after registering the interrupt handler with devm_request_irq(). If an interrupt occurred before init_completion() was called, the interrupt service routine spear_adc_isr() would call complete() on an uninitialized completion structure. This caused the kernel to dereference a NULL pointer and triggered a Kernel Address Sanitizer (KASAN) wild-memory-access error, potentially leading to a kernel panic. The fix involved moving the init_completion() call to before devm_request_irq() to ensure the completion is properly initialized before any interrupts can occur.
Potential Impact
This vulnerability could cause a kernel panic due to a race condition in the interrupt handling of the spear ADC driver. The kernel panic results from dereferencing an uninitialized completion object, which may lead to denial of service on affected systems. There is no indication of privilege escalation or arbitrary code execution from the provided data.
Mitigation Recommendations
A fix is available that moves the initialization of the completion object before the interrupt request registration to prevent the race condition. Users should update their Linux kernel to a version that includes this fix. Since no vendor advisory or patch links are provided, check the official Linux kernel repositories or distributions for the patched version. Patch status is not yet confirmed in the provided data — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7gcx-pfrf-w3c4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64602"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cfa0bf8831d5391b0781
Added to database: 08/06/2026, 18:17:04 UTC
Last enriched: 08/06/2026, 19:12:09 UTC
Last updated: 08/07/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.