0.0
NA
CVE-2026-31687
gpio: 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().

INFO

Published Date :

April 27, 2026, 6:16 p.m.

Last Modified :

April 27, 2026, 6:32 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-31687 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Correctly register and unregister the driver in module init/exit.
  • Register driver in module initcall.
  • Unregister driver in module exit.
  • Avoid driver registration in probe callbacks.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-31687 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-31687 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-31687 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-31687 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 27, 2026

    Action Type Old Value New Value
    Added 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().
    Added Reference https://git.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854
    Added Reference https://git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308
    Added Reference https://git.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54c
    Added Reference https://git.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
    Added Reference https://git.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687
    Added Reference https://git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79
    Added Reference https://git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12
    Added Reference https://git.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435f
    Added Reference https://git.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25
    Added Reference https://git.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033
    Added Reference https://git.kernel.org/stable/c/a7fa9460b86f810913b6779461d0448e7c11214c
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.