CVE Intelligence
Medium

CVE-2026-31687 — gpio: omap: do not register driver in probe()

In the Linux kernel, the following vulnerability has been resolved: gpio: omap: do not register driver in probe() Commit 11a78b794496 ("ARM: OMAP: MPUIO wake updates") registers the omap_mpuio_driver from omap_mpuio_init(), which is called from omap_gpio_probe(). However, it neither makes sense to register drivers from probe() callbacks of other drivers, nor does the driver core allow registering drivers with a device lock already being held. The latter was revealed by commit dc23806a7c47 ("driver core: enforce device_lock for driver_match_device()") leading to a potential deadlock condition described in [1]. Additionally, the omap_mpuio_driver is never unregistered from the driver core, even if the module is unloaded. Hence, register the omap_mpuio_driver from the module initcall and unregister it in module_exit().

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

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.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

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.13%
ahead of 2% of scored CVEs · Oct 15, 2026
Affects
Linux
Linux and 1 more
CVSS base
5.5
Medium · 1 source(s)

Remediation

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

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 86588916e1887a5edb8a9161cd7ae81e47a7ed25version 2.6.22≥ 6.19.1 and < 6.19.2≥ 6.18.11 and < 6.18.12≥ 6.12.72 and < 6.12.73≥ 6.6.125 and < 6.6.126≥ bc82e5f4d7dc8237ae8cabc73aa46fc93c85d98c and < 03db4dc9ad6eb91e640b517e00373ce877682854≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 730e5ebff40c852e3ea57b71bf02a4b89c69435f
and 8 more ≥ 8d76b2488eb3cc0717ab81b60622cff4a5f90f79 and < 53a76425e0764421ba93bb9045d2e454667d5687≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 32f08c3ddd6dda6cbb6c9d715de10f21dccde50f≥ cd0e0a76e40c2e77bcfc88291d00dca22b00158e and < a7fa9460b86f810913b6779461d0448e7c11214c≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 2211d77892913804d16c28c7415b82804ab1e54c≥ adc1796eced46b48e23ec200a219d635f33a38ee and < 673dafb9a86349a12a93151fd467625614dc7e12≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 1c04c3a4de8d4bcb9202f94c44f26c57c2572308≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < a29215961d833f4de33a09c3964d31ebc6083033≥ 11a78b7944963a8b052be46108d07a3ced9e2762 and < 57bcd3feffa79544c73a1a1872472389a391cc79
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel ≥ 2.6.22 and < 5.10.251version 6.19-rc7version 6.19-rc6version 6.19-rc5version 6.19-rc4version 6.19-rc3version 6.19-rc2version 6.19-rc1
and 5 more ≥ 6.13 and < 6.18.11≥ 6.7 and < 6.12.72≥ 6.2 and < 6.6.125≥ 5.16 and < 6.1.164≥ 5.11 and < 5.15.201
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-667

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.13%

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Apr 27, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor
CWE-667
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d

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 CISA SSVC assessment.
  • 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-31687 is "gpio: omap: do not register driver in probe()", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.13% 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.

Sign in or create an account to comment and suggest corrections.