CVE-2026-80562

CVE CVE-2026-80562EUVD EUVD-2026-66477Published 2026-08-26T14:37:27.000ZLast changed 2026-08-27T12:40:17.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.1.10; patch: 5.10.267; 54be566317b6aece2389a95bb19ea209af9359be <b6505a4cea45dd92eb753581b1ad9b524b5fcc34; patch: 5.15.218; patch: 6.18.46; 54be566317b6aece2389a95bb19ea209af9359be <600411ea1f2443fdf5b1af9b6480f616d7aff9d0; patch: 6.12.106; 54be566317b6aece2389a95bb19ea209af9359be <bc7934d0acd4fc1c7e5b7c68debdb4a991121628; patch: 0; 54be566317b6aece2389a95bb19ea209af9359be <0559b86611c35d342dd48542ea26a9e437046bf6; patch: 6.6.154; 54be566317b6aece2389a95bb19ea209af9359be <431b10133113537660a6090a2856b0d74d1b06de; 54be566317b6aece2389a95bb19ea209af9359be <84be002b40d30c56a91873b236e2d9001bbee363; 3.2; 54be566317b6aece2389a95bb19ea209af9359be <63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c; 54be566317b6aece2389a95bb19ea209af9359be <359e6b1168c9a62a7bd214ace476aaa2d57eebe8; patch: 7.2; patch: 6.1.185

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.