CVE-2026-64429gpio: eic-sprd: use raw_spinlock_t in the irq startup path
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 25518e024e3a6e5715d672f1daa91e1d100f7436 before 96612bf2712cd961dbd9b52f3a9b4ab668f57628; 25518e024e3a6e5715d672f1daa91e1d100f7436 builds before 581ac2ad001ff1128931191f249a7f2074672b7a; from 25518e024e3a6e5715d672f1daa91e1d100f7436 before e244cd8b51001ba480f274c44dba9002813a4739; 25518e024e3a6e5715d672f1daa91e1d100f7436 builds before 19d63fd528719ce7d06d9aeb88d25b7d6478198a; 25518e024e3a6e5715d672f1daa91e1d100f7436 builds before 6112fba4150039ccd90e29f2d1b788c73ad7b3dd; from 25518e024e3a6e5715d672f1daa91e1d100f7436 before 4750909a40da9016185e0ac991510a278cecb1e7; 25518e024e3a6e5715d672f1daa91e1d100f7436 builds before 5c3c9ec1172a4c3384b8b800b3a8896cc2c1b20e; 25518e024e3a6e5715d672f1daa91e1d100f7436 builds before 90f0109019e6817eb40a486671b7722d1544ae29 | CNA record |
linux linux_kernel linux:linux_kernel | from 4.17 before 5.10.261; from 5.11 before 5.15.212; from 5.16 before 6.1.178; from 6.2 before 6.6.145; from 6.7 before 6.12.96; from 6.13 before 6.18.39; from 6.19 before 7.1.4 | NVD |
References
- https://git.kernel.org/stable/c/96612bf2712cd961dbd9b52f3a9b4ab668f57628patch
- https://git.kernel.org/stable/c/581ac2ad001ff1128931191f249a7f2074672b7apatch
- https://git.kernel.org/stable/c/e244cd8b51001ba480f274c44dba9002813a4739patch
- https://git.kernel.org/stable/c/19d63fd528719ce7d06d9aeb88d25b7d6478198apatch
- https://git.kernel.org/stable/c/6112fba4150039ccd90e29f2d1b788c73ad7b3ddpatch
- https://git.kernel.org/stable/c/4750909a40da9016185e0ac991510a278cecb1e7patch
- https://git.kernel.org/stable/c/5c3c9ec1172a4c3384b8b800b3a8896cc2c1b20epatch
- https://git.kernel.org/stable/c/90f0109019e6817eb40a486671b7722d1544ae29patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.