CVE-2026-31687 Details
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().
A vulnerability exists in the Linux kernel's OMAP GPIO driver related to how the OMAP MPU Input/Output (MPUIO) driver is registered. The OMAP MPUIO driver is registered during the GPIO probe process, which is not a suitable practice. This registration method can lead to a deadlock, as the driver core does not permit registering drivers while holding a device lock, a condition introduced by a recent change in the driver core. Furthermore, the OMAP MPUIO driver is not properly unregistered when the module is unloaded, creating potential for resource leaks or undefined behavior.
The OMAP MPUIO driver should be registered during the module initialization phase and unregistered during the module exit phase, rather than being registered from within the GPIO probe callback.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 2.6.22, < 5.10.251 >= 5.11, < 5.15.201 >= 5.16, < 6.1.164 >= 6.2, < 6.6.125 >= 6.7, < 6.12.72 >= 6.13, < 6.18.11 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 6.19 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 11, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 6, 2026 | Initial Analysis | [email protected] |
| Apr 27, 2026 | New CVE Received | kernel.org |