CVE-2026-74468

Not scored yetLast modified Aug 19, 2026

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

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < efc76a3f5353dd33a2e2ad48200cd4a18de30a0d; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < 935e6872db7faecfbe1a10b3f5d97a62fdff5ec9; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < 98f292cb6d01487d17988d9fd4e19c13e7adb156; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < 16da33cb36e663b6967112185e11d00ce8ff957c; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < ff050589a21967883bb55f6dba42568f8367ad4a; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < 466ab0c41d5f54f71cee60619d07c4abd0ffd2cd; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < c0a4ec89fc26e4b679b04f1002c503cb2529acdc; >= 38eb18a6f92da886fc1af509d25e8f7a49e23d9a, < a02b8950d619123da64f69b70fe1dadef217dfe4
LinuxLinux3.2

References

Timeline

Published
Aug 15, 2026
Last modified
Aug 19, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-744698.8In the Linux kernel, the following vulnerability has been resolved: sctp: prevent peer transport count overflow sctp_assoc_add_peer() incrCVE-2026-74476.3A flaw has been found in SourceCodester Pet Grooming Management Software 1.0. This vulnerability affects unknown code of the file /admin/updCVE-2026-744707.8In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write resp_CVE-2026-744717.8In the Linux kernel, the following vulnerability has been resolved: tracing: Check return value of __register_event() in trace_module_add_eCVE-2026-74472In the Linux kernel, the following vulnerability has been resolved: ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev() ublk_cCVE-2026-744739.8In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() in route_shortcircuit() route_shortCVE-2026-744749.8In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() for transmit path header pulls In vCVE-2026-7447510.0In the Linux kernel, the following vulnerability has been resolved: vxlan: use neigh_ha_snapshot() in route_shortcircuit() The neighbour hCVE-2026-744769.1In the Linux kernel, the following vulnerability has been resolved: veth: convert frag_list skbs before running XDP A frag_list skb can reCVE-2026-74477In the Linux kernel, the following vulnerability has been resolved: uprobes: Fix NULL pointer dereference in hprobe_expire() Forking a tasCVE-2026-744789.8In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rxCVE-2026-744797.8In the Linux kernel, the following vulnerability has been resolved: net: pktgen: fix proc entry use-after-free pktgen_change_name() replac
CVE-2026-74468: Unscored | Vulnix