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-74468gpio: pch: use raw_spinlock_t for the register lock

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: pch: use raw_spinlock_t for the register lock pch_irq_type() is registered as the irq_chip .irq_set_type callback and takes chip->spinlock with spin_lock_irqsave(). This callback is reached from __setup_irq() -> __irq_set_trigger() -> chip->irq_set_type() while the caller holds desc->lock, a raw_spinlock_t, with hardirqs disabled. That context is not sleepable, but on PREEMPT_RT a regular spinlock_t is an rtmutex-backed sleeping lock, so acquiring it there is invalid. This was confirmed on a PREEMPT_RT kernel with lockdep (PROVE_RAW_LOCK_NESTING and DEBUG_ATOMIC_SLEEP). A grounded PoC mirrored pch_irq_type()'s locking and drove it through the real genirq carrier irq_set_irq_type() -> __irq_set_trigger() -> chip->irq_set_type(), i.e. the same __irq_set_trigger() edge that __setup_irq() takes for a requested IRQ. With the original spin_lock_irqsave() edge lockdep reported an invalid wait context, immediately followed by: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 95, name: insmod hardirqs last disabled at (3784): _raw_spin_lock_irqsave+0x4f/0x60 rt_spin_lock+0x3a/0x1c0 repro_irq_set_type+0x64/0xa0 [pch_repro] __irq_set_trigger+0x69/0x140 irq_set_irq_type+0x78/0xd0 Switching the mirrored lock to raw_spinlock_t made both splats go away. Convert the register lock to raw_spinlock_t. The same lock also serializes the GPIO direction/value callbacks and the suspend/resume register save/restore, but all of those critical sections only perform MMIO register accesses (ioread32()/iowrite32()) and irq_set_handler_locked(); none of them contain sleepable operations. Keeping this register lock non-sleeping is therefore appropriate for the irqchip callbacks and does not change the GPIO-side locking contract. This is the same class of issue and fix as recently addressed for other GPIO controllers, e.g. commit 286533cb14a3 ("gpio: sch: use raw_spinlock_t in the irq startup path") and commit 90f0109019e6 ("gpio: eic-sprd: use raw_spinlock_t in the irq startup path").

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < efc76a3f5353dd33a2e2ad48200cd4a18de30a0d
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < 935e6872db7faecfbe1a10b3f5d97a62fdff5ec9
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < 98f292cb6d01487d17988d9fd4e19c13e7adb156
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < 16da33cb36e663b6967112185e11d00ce8ff957c
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < ff050589a21967883bb55f6dba42568f8367ad4a
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < 466ab0c41d5f54f71cee60619d07c4abd0ffd2cd
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < c0a4ec89fc26e4b679b04f1002c503cb2529acdc
    • affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a – < a02b8950d619123da64f69b70fe1dadef217dfe4
  • Linux · Linux

    • affected 3.2
    • unaffected < 3.2
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 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-74468 badge
[![CVE-2026-74468](https://cveledger.app/badge/CVE-2026-74468.svg)](https://cveledger.app/cve/CVE-2026-74468)

Record last updated .