0.0
NA
CVE-2026-64429
gpio: eic-sprd: use raw_spinlock_t in the irq startup path
Description

In the Linux kernel, the following vulnerability has been resolved: gpio: eic-sprd: use raw_spinlock_t in the irq startup path sprd_eic_irq_unmask() enables the GPIO IRQ and then updates controller state through sprd_eic_update(), which takes sprd_eic->lock with spin_lock_irqsave(). The callback can be reached from irq_startup() while setting up a requested IRQ. That path is not sleepable, but on PREEMPT_RT a regular spinlock_t becomes a sleeping lock. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the request_threaded_irq() -> __setup_irq() -> irq_startup() -> sprd_eic_irq_unmask() -> sprd_eic_update() carrier and used the original spin_lock_irqsave(&sprd_eic->lock) edge. Lockdep BUG: sleeping function called from invalid context hardirqs last disabled at ... __setup_irq.constprop.0 ... [vuln_msv] sprd_rt_spin_lock_irqsave+0x1c/0x30 [vuln_msv] sprd_eic_update.constprop.0+0x48/0x90 [vuln_msv] sprd_eic_irq_unmask.constprop.0+0x35/0x50 [vuln_msv] __setup_irq.constprop.0+0xd/0x30 [vuln_msv] Convert the Spreadtrum EIC controller lock to raw_spinlock_t. The locked section only serializes MMIO register updates and does not contain sleepable operations, so keeping it non-sleeping is appropriate for the irqchip callbacks.

INFO

Published Date :

July 25, 2026, 10:17 a.m.

Last Modified :

July 25, 2026, 10:17 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64429 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Convert the controller lock to raw_spinlock_t for non-sleeping operations.
  • Convert the controller lock to raw_spinlock_t.
  • Ensure locked sections do not contain sleepable operations.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64429 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64429 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64429 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64429 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 25, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '96612bf2712cd961dbd9b52f3a9b4ab668f57628', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '581ac2ad001ff1128931191f249a7f2074672b7a', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': 'e244cd8b51001ba480f274c44dba9002813a4739', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '19d63fd528719ce7d06d9aeb88d25b7d6478198a', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '6112fba4150039ccd90e29f2d1b788c73ad7b3dd', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '4750909a40da9016185e0ac991510a278cecb1e7', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '5c3c9ec1172a4c3384b8b800b3a8896cc2c1b20e', 'versionType': 'git'}, {'status': 'affected', 'version': '25518e024e3a6e5715d672f1daa91e1d100f7436', 'lessThan': '90f0109019e6817eb40a486671b7722d1544ae29', 'versionType': 'git'}], 'programFiles': ['drivers/gpio/gpio-eic-sprd.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.17'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.17', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpio/gpio-eic-sprd.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: gpio: eic-sprd: use raw_spinlock_t in the irq startup path sprd_eic_irq_unmask() enables the GPIO IRQ and then updates controller state through sprd_eic_update(), which takes sprd_eic->lock with spin_lock_irqsave(). The callback can be reached from irq_startup() while setting up a requested IRQ. That path is not sleepable, but on PREEMPT_RT a regular spinlock_t becomes a sleeping lock. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the request_threaded_irq() -> __setup_irq() -> irq_startup() -> sprd_eic_irq_unmask() -> sprd_eic_update() carrier and used the original spin_lock_irqsave(&sprd_eic->lock) edge. Lockdep BUG: sleeping function called from invalid context hardirqs last disabled at ... __setup_irq.constprop.0 ... [vuln_msv] sprd_rt_spin_lock_irqsave+0x1c/0x30 [vuln_msv] sprd_eic_update.constprop.0+0x48/0x90 [vuln_msv] sprd_eic_irq_unmask.constprop.0+0x35/0x50 [vuln_msv] __setup_irq.constprop.0+0xd/0x30 [vuln_msv] Convert the Spreadtrum EIC controller lock to raw_spinlock_t. The locked section only serializes MMIO register updates and does not contain sleepable operations, so keeping it non-sleeping is appropriate for the irqchip callbacks.
    Added Reference https://git.kernel.org/stable/c/19d63fd528719ce7d06d9aeb88d25b7d6478198a
    Added Reference https://git.kernel.org/stable/c/4750909a40da9016185e0ac991510a278cecb1e7
    Added Reference https://git.kernel.org/stable/c/581ac2ad001ff1128931191f249a7f2074672b7a
    Added Reference https://git.kernel.org/stable/c/5c3c9ec1172a4c3384b8b800b3a8896cc2c1b20e
    Added Reference https://git.kernel.org/stable/c/6112fba4150039ccd90e29f2d1b788c73ad7b3dd
    Added Reference https://git.kernel.org/stable/c/90f0109019e6817eb40a486671b7722d1544ae29
    Added Reference https://git.kernel.org/stable/c/96612bf2712cd961dbd9b52f3a9b4ab668f57628
    Added Reference https://git.kernel.org/stable/c/e244cd8b51001ba480f274c44dba9002813a4739
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.