Unknown

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

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.

Published Aug 26, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 12% of scored CVEs · Oct 27, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 54be566317b6aece2389a95bb19ea209af9359be and < 431b10133113537660a6090a2856b0d74d1b06de≥ 54be566317b6aece2389a95bb19ea209af9359be and < 359e6b1168c9a62a7bd214ace476aaa2d57eebe8≥ 54be566317b6aece2389a95bb19ea209af9359be and < 63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c≥ 54be566317b6aece2389a95bb19ea209af9359be and < b6505a4cea45dd92eb753581b1ad9b524b5fcc34≥ 54be566317b6aece2389a95bb19ea209af9359be and < 84be002b40d30c56a91873b236e2d9001bbee363≥ 54be566317b6aece2389a95bb19ea209af9359be and < bc7934d0acd4fc1c7e5b7c68debdb4a991121628≥ 54be566317b6aece2389a95bb19ea209af9359be and < 0559b86611c35d342dd48542ea26a9e437046bf6≥ 54be566317b6aece2389a95bb19ea209af9359be and < 600411ea1f2443fdf5b1af9b6480f616d7aff9d0 and 1 more version 3.2	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 26, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/359e6b1168c9a62a7bd214ace476aaa2d57eebe8
NIST National Vulnerability Database
git.kernel.org/stable/c/600411ea1f2443fdf5b1af9b6480f616d7aff9d0
NIST National Vulnerability Database
git.kernel.org/stable/c/431b10133113537660a6090a2856b0d74d1b06de
NIST National Vulnerability Database
git.kernel.org/stable/c/63d2230e5076c12f93d2a1d1bff2fbbf6cf32f3c
NIST National Vulnerability Database
git.kernel.org/stable/c/b6505a4cea45dd92eb753581b1ad9b524b5fcc34
NIST National Vulnerability Database
git.kernel.org/stable/c/bc7934d0acd4fc1c7e5b7c68debdb4a991121628
NIST National Vulnerability Database
git.kernel.org/stable/c/0559b86611c35d342dd48542ea26a9e437046bf6
NIST National Vulnerability Database
git.kernel.org/stable/c/84be002b40d30c56a91873b236e2d9001bbee363
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 5h
Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 5h
Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 5h
Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 5h
Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 5h
Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 5h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80562 is "gpio: ml-ioh: use raw_spinlock_t for the register lock", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.