๐Ÿ” CVE Alert

CVE-2026-74468

UNKNOWN 0.0

gpio: pch: use raw_spinlock_t for the register lock

CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th

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

Vendor linux
Product linux
Ecosystems
Industries
Technology
Published Aug 15, 2026
Stay Ahead of the Next One

Get instant alerts for linux linux

Be the first to know when new unknown vulnerabilities affecting linux linux are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

Affected Versions

Linux / Linux
38eb18a6f92da886fc1af509d25e8f7a49e23d9a < 16da33cb36e663b6967112185e11d00ce8ff957c 38eb18a6f92da886fc1af509d25e8f7a49e23d9a < ff050589a21967883bb55f6dba42568f8367ad4a 38eb18a6f92da886fc1af509d25e8f7a49e23d9a < 466ab0c41d5f54f71cee60619d07c4abd0ffd2cd 38eb18a6f92da886fc1af509d25e8f7a49e23d9a < c0a4ec89fc26e4b679b04f1002c503cb2529acdc 38eb18a6f92da886fc1af509d25e8f7a49e23d9a < a02b8950d619123da64f69b70fe1dadef217dfe4
Linux / Linux
3.2

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
git.kernel.org: https://git.kernel.org/stable/c/16da33cb36e663b6967112185e11d00ce8ff957c git.kernel.org: https://git.kernel.org/stable/c/ff050589a21967883bb55f6dba42568f8367ad4a git.kernel.org: https://git.kernel.org/stable/c/466ab0c41d5f54f71cee60619d07c4abd0ffd2cd git.kernel.org: https://git.kernel.org/stable/c/c0a4ec89fc26e4b679b04f1002c503cb2529acdc git.kernel.org: https://git.kernel.org/stable/c/a02b8950d619123da64f69b70fe1dadef217dfe4