CVE-2026-80562

In the Linux kernel, the following vulnerability has been resolved: gpio: ml-ioh: use raw_spinlock_t for the register lock ioh_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. ioh_irq_enable() and ioh_irq_disable() take the same lock from the .irq_enable/.irq_disable callbacks, which are likewise invoked with desc->lock held. 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, and those critical sections only perform short sequences of MMIO register accesses (ioread32()/iowrite32()); the .irq_set_type callback additionally emits a dev_warn() on an unsupported type. None of these are sleepable operations, so keeping this register lock non-sleeping is appropriate for the irqchip callbacks and does not change the GPIO-side locking contract. This is the same fix as commit a02b8950d619 ("gpio: pch: use raw_spinlock_t for the register lock"); this driver shares the same structure as gpio-pch.

• https://git.kernel.org/stable/c/0559b86611c35d342dd48542ea26a9e437046bf6
• https://git.kernel.org/stable/c/359e6b1168c9a62a7bd214ace476aaa2d57eebe8
• https://git.kernel.org/stable/c/431b10133113537660a6090a2856b0d74d1b06de
• https://git.kernel.org/stable/c/600411ea1f2443fdf5b1af9b6480f616d7aff9d0
• https://git.kernel.org/stable/c/63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c
• https://git.kernel.org/stable/c/84be002b40d30c56a91873b236e2d9001bbee363
• https://git.kernel.org/stable/c/b6505a4cea45dd92eb753581b1ad9b524b5fcc34
• https://git.kernel.org/stable/c/bc7934d0acd4fc1c7e5b7c68debdb4a991121628

Published

Aug 26, 2026

Last Modified

Aug 27, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-80557In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-80558In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-80559In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-8056IBM Langflow OSS 1.0.0 through 1.10.0 allows authenticated u…8.8
• CVE-2026-80560In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80561In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-80565In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80568In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80569In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80570In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80572In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-80573In the Linux kernel, the following vulnerability has been re…