Linux Kernel up to 7.2-rc2 Spear ADC Driver spear_adc.c spear_adc_probe uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k1.20

Summaryinfo

A vulnerability categorized as critical has been discovered in Linux Kernel up to 7.2-rc2. Affected is the function spear_adc_probe of the file drivers/iio/adc/spear_adc.c of the component Spear ADC Driver. Executing a manipulation can lead to uninitialized pointer. This vulnerability is handled as CVE-2026-64602. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 7.2-rc2. This vulnerability affects the function spear_adc_probe of the file drivers/iio/adc/spear_adc.c of the component Spear ADC Driver. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. As an impact it is known to affect availability. CVE summarizes:

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

The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-64602 since 07/19/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/06/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc3 eliminates this vulnerability. Applying the patch aea8ae6c4d3ed58d9223360f758df6bd8b90c608/67a49ab41320b3f721ce4be7447754ff040acbd5/a50757398794aaa25f908b96c6733e045466cba4/f3f90bc7b38ba3ff14f131cea0f8eb77624787a8/37077d8271b1f24894fbc21bca1c4cd337525d31/bbfebae473ac2c8a194523b29ccb9b45f02f134c/eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4/3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0 is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc3
Patch: aea8ae6c4d3ed58d9223360f758df6bd8b90c608/67a49ab41320b3f721ce4be7447754ff040acbd5/a50757398794aaa25f908b96c6733e045466cba4/f3f90bc7b38ba3ff14f131cea0f8eb77624787a8/37077d8271b1f24894fbc21bca1c4cd337525d31/bbfebae473ac2c8a194523b29ccb9b45f02f134c/eb5b07c9d0ec1a9d4b6871b14793c19967d79dc4/3ee2128b6f0eb0be7b6cb8f6e0f1f113a65201a0

Timelineinfo

07/19/2026 CVE reserved
08/06/2026 +18 days Advisory disclosed
08/06/2026 +0 days VulDB entry created
08/06/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64602 (🔒)
GCVE (CVE): GCVE-0-2026-64602
GCVE (VulDB): GCVE-100-386506

Entryinfo

Created: 08/06/2026 09:54
Changes: 08/06/2026 09:54 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!