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-31687gpio: omap: do not register driver in probe()

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. · 49 days later

    Published

  3. · 26 days 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

CVSS scores of CVE-2026-31687, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 57bcd3feffa79544c73a1a1872472389a391cc79
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 86588916e1887a5edb8a9161cd7ae81e47a7ed25
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < a29215961d833f4de33a09c3964d31ebc6083033
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 1c04c3a4de8d4bcb9202f94c44f26c57c2572308
    • affected adc1796eced46b48e23ec200a219d635f33a38ee – < 673dafb9a86349a12a93151fd467625614dc7e12
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 2211d77892913804d16c28c7415b82804ab1e54c
    • affected cd0e0a76e40c2e77bcfc88291d00dca22b00158e – < a7fa9460b86f810913b6779461d0448e7c11214c
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
    • affected 8d76b2488eb3cc0717ab81b60622cff4a5f90f79 – < 53a76425e0764421ba93bb9045d2e454667d5687
    • affected 11a78b7944963a8b052be46108d07a3ced9e2762 – < 730e5ebff40c852e3ea57b71bf02a4b89c69435f
    • affected bc82e5f4d7dc8237ae8cabc73aa46fc93c85d98c – < 03db4dc9ad6eb91e640b517e00373ce877682854
    • affected 6.6.125 – < 6.6.126
    • affected 6.12.72 – < 6.12.73
    • affected 6.18.11 – < 6.18.12
    • affected 6.19.1 – < 6.19.2
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 5.10.251 – ≤ 5.10.*
    • unaffected 5.15.201 – ≤ 5.15.*
    • unaffected 6.1.164 – ≤ 6.1.*
    • unaffected 6.6.125 – ≤ 6.6.*
    • unaffected 6.6.126 – ≤ 6.6.*
    • unaffected 6.12.72 – ≤ 6.12.*
    • unaffected 6.12.73 – ≤ 6.12.*
    • unaffected 6.18.11 – ≤ 6.18.*
    • unaffected 6.18.12 – ≤ 6.18.*
    • unaffected 6.19.2 – ≤ 6.19.*
    • unaffected 6.19 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .