Heimdall Security Logo

CVE-2026-80562

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.1.185, <=6.1.*, <3.2, <=6.12.*, 6.12.106, 0, 5.10.267, <=7.1.*, 6.6.154, <431b10133113537660a6090a2856b0d74d1b06de, <bc7934d0acd4fc1c7e5b7c68debdb4a991121628, <359e6b1168c9a62a7bd214ace476aaa2d57eebe8, <=5.10.*, <=6.6.*, <0559b86611c35d342dd48542ea26a9e437046bf6, <63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c, <=6.18.*, 3.2, 7.1.10, <b6505a4cea45dd92eb753581b1ad9b524b5fcc34, 54be566317b6aece2389a95bb19ea209af9359be, <=*, <=5.15.*, 6.18.46, <600411ea1f2443fdf5b1af9b6480f616d7aff9d0, 7.2, 5.15.218, <84be002b40d30c56a91873b236e2d9001bbee363

Description

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.

Gravité et risque d'exploitation

CVE-2026-80562 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.22 %, ce qui la place devant 11.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.1.185, <=6.1.*, <3.2, <=6.12.*, 6.12.106, 0, 5.10.267, <=7.1.*, 6.6.154, <431b10133113537660a6090a2856b0d74d1b06de, <bc7934d0acd4fc1c7e5b7c68debdb4a991121628, <359e6b1168c9a62a7bd214ace476aaa2d57eebe8, <=5.10.*, <=6.6.*, <0559b86611c35d342dd48542ea26a9e437046bf6, <63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c, <=6.18.*, 3.2, 7.1.10, <b6505a4cea45dd92eb753581b1ad9b524b5fcc34, 54be566317b6aece2389a95bb19ea209af9359be, <=*, <=5.15.*, 6.18.46, <600411ea1f2443fdf5b1af9b6480f616d7aff9d0, 7.2, 5.15.218, <84be002b40d30c56a91873b236e2d9001bbee363) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE