CVE-2026-31687

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 27, 2026

Last Modified

May 6, 2026

Advisory Details (10)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435f
generic

Revert "driver core: enforce device_lock for driver_match_device()" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79
generic

Revert "driver core: enforce device_lock for driver_match_device()" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54c
generic

gpio: omap: do not register driver in probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308
generic

Revert "driver core: enforce device_lock for driver_match_device()" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.251—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (101 versions)6.18.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(23)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 184 total refreshes for this CVE.

  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-04 01:46 UTCOSV refresh
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 13:53 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-24 14:17 UTCEPSS rescore
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 14:02 UTCEG score recompute
  22. 2026-08-17 14:02 UTCVendor advisory
  23. 2026-08-17 14:02 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 05:37 UTCEG score recompute
  2. 2026-08-16 05:37 UTCVendor advisory
  3. 2026-08-16 05:37 UTCGHSA enrichment
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:58 UTCEG score recompute
  6. 2026-08-15 01:58 UTCVendor advisory
  7. 2026-08-15 01:58 UTCGHSA enrichment
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 04:01 UTCVendor advisory
  10. 2026-08-14 04:01 UTCGHSA enrichment
  11. 2026-08-12 21:55 UTCVendor advisory
  12. 2026-08-12 21:55 UTCGHSA enrichment
  13. 2026-08-11 23:58 UTCEG score recompute
  14. 2026-08-11 23:58 UTCVendor advisory
  15. 2026-08-11 23:58 UTCGHSA enrichment
  16. 2026-08-11 02:01 UTCEG score recompute
  17. 2026-08-11 02:01 UTCVendor advisory
  18. 2026-08-11 02:01 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 01:09 UTCEG score recompute
  21. 2026-08-10 01:09 UTCVendor advisory
  22. 2026-08-10 01:09 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 03:11 UTCEG score recompute
  25. 2026-08-09 03:11 UTCVendor advisory
  26. 2026-08-09 03:11 UTCGHSA enrichment
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-07 18:52 UTCEG score recompute
  29. 2026-08-07 18:52 UTCVendor advisory
  30. 2026-08-07 18:52 UTCGHSA enrichment
  31. 2026-08-06 20:46 UTCEG score recompute
  32. 2026-08-06 20:46 UTCVendor advisory
  33. 2026-08-06 20:46 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-05 22:48 UTCEG score recompute
  36. 2026-08-05 22:48 UTCVendor advisory
  37. 2026-08-05 22:48 UTCGHSA enrichment
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-03 20:52 UTCVendor advisory
  41. 2026-08-03 20:52 UTCGHSA enrichment
  42. 2026-08-02 10:22 UTCEG score recompute
  43. 2026-08-02 10:22 UTCVendor advisory
  44. 2026-08-02 10:22 UTCGHSA enrichment
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 16:28 UTCEPSS rescore
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-28 15:36 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-25 14:17 UTCEPSS rescore
  51. 2026-07-24 14:17 UTCEPSS rescore
  52. 2026-07-23 03:08 UTCEG score recompute
  53. 2026-07-22 14:08 UTCEPSS rescore
  54. 2026-07-22 14:08 UTCEPSS rescore
  55. 2026-07-20 17:08 UTCEPSS rescore
  56. 2026-07-20 17:08 UTCEPSS rescore
  57. 2026-07-19 21:38 UTCOSV refresh
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-18 10:04 UTCEPSS rescore
  60. 2026-07-16 17:03 UTCEPSS rescore
  61. 2026-07-16 17:03 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-13 22:30 UTCEPSS rescore
  65. 2026-07-13 06:13 UTCEPSS rescore
  66. 2026-07-13 06:13 UTCEPSS rescore
  67. 2026-07-12 05:46 UTCEPSS rescore
  68. 2026-07-11 08:27 UTCEPSS rescore
  69. 2026-07-09 19:10 UTCEPSS rescore
  70. 2026-07-08 15:15 UTCEPSS rescore
  71. 2026-07-07 13:46 UTCEPSS rescore
  72. 2026-07-06 16:27 UTCEPSS rescore
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-04 06:31 UTCEPSS rescore
  75. 2026-07-01 15:06 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31687?
CVE-2026-31687 is a medium vulnerability published on April 27, 2026. 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 omapmpuiodriver from omapmpuioinit(), which is called from omapgpioprobe(). However, it neither makes sense to…
When was CVE-2026-31687 disclosed?
CVE-2026-31687 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31687 actively exploited?
CVE-2026-31687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31687?
CVE-2026-31687 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31687, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31687

Explore →

Is Your Infrastructure Affected by CVE-2026-31687?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs