Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80562gpio: ml-ioh: use raw_spinlock_t for the register lock

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 431b10133113537660a6090a2856b0d74d1b06de
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 359e6b1168c9a62a7bd214ace476aaa2d57eebe8
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < b6505a4cea45dd92eb753581b1ad9b524b5fcc34
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 84be002b40d30c56a91873b236e2d9001bbee363
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < bc7934d0acd4fc1c7e5b7c68debdb4a991121628
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 0559b86611c35d342dd48542ea26a9e437046bf6
    • affected 54be566317b6aece2389a95bb19ea209af9359be – < 600411ea1f2443fdf5b1af9b6480f616d7aff9d0
  • Linux · Linux

    • affected 3.2
    • unaffected < 3.2
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80562 badge
[![CVE-2026-80562](https://cveledger.app/badge/CVE-2026-80562.svg)](https://cveledger.app/cve/CVE-2026-80562)

Record last updated .