Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64429gpio: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64429, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 96612bf2712cd961dbd9b52f3a9b4ab668f57628
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 581ac2ad001ff1128931191f249a7f2074672b7a
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < e244cd8b51001ba480f274c44dba9002813a4739
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 19d63fd528719ce7d06d9aeb88d25b7d6478198a
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 6112fba4150039ccd90e29f2d1b788c73ad7b3dd
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 4750909a40da9016185e0ac991510a278cecb1e7
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 5c3c9ec1172a4c3384b8b800b3a8896cc2c1b20e
    • affected 25518e024e3a6e5715d672f1daa91e1d100f7436 – < 90f0109019e6817eb40a486671b7722d1544ae29
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64429 badge
[![CVE-2026-64429](https://cveledger.app/badge/CVE-2026-64429.svg)](https://cveledger.app/cve/CVE-2026-64429)

Record last updated .