CVE-2026-80562

published 26 Aug 2026 · updated 23 Sep 2026

gpio: ml-ioh: use raw_spinlock_t for the register lock

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0559b86611c35d342dd48542ea26a9e437046bf6, Kernel 359e6b1168c9a62a7bd214ace476aaa2d57eebe8, Kernel 431b10133113537660a6090a2856b0d74d1b06de and 5 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.2, >=54be566317b6aece2389a95bb19ea209af9359be <0559b86611c35d342dd48542ea26a9e437046bf6, >=54be566317b6aece2389a95bb19ea209af9359be <359e6b1168c9a62a7bd214ace476aaa2d57eebe8, >=54be566317b6aece2389a95bb19ea209af9359be <431b10133113537660a6090a2856b0d74d1b06de, >=54be566317b6aece2389a95bb19ea209af9359be <600411ea1f2443fdf5b1af9b6480f616d7aff9d0, >=54be566317b6aece2389a95bb19ea209af9359be <63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c, >=54be566317b6aece2389a95bb19ea209af9359be <84be002b40d30c56a91873b236e2d9001bbee363, >=54be566317b6aece2389a95bb19ea209af9359be <b6505a4cea45dd92eb753581b1ad9b524b5fcc34, >=54be566317b6aece2389a95bb19ea209af9359be <bc7934d0acd4fc1c7e5b7c68debdb4a9911216280559b86611c35d342dd48542ea26a9e437046bf6, 359e6b1168c9a62a7bd214ace476aaa2d57eebe8, 431b10133113537660a6090a2856b0d74d1b06de, 600411ea1f2443fdf5b1af9b6480f616d7aff9d0, 63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c, 84be002b40d30c56a91873b236e2d9001bbee363, b6505a4cea45dd92eb753581b1ad9b524b5fcc34, bc7934d0acd4fc1c7e5b7c68debdb4a991121628

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80562 severity on Zeptric[![CVE-2026-80562](https://zeptric.io/badge/cve/CVE-2026-80562.svg)](https://zeptric.io/cve/CVE-2026-80562)