CVE-2026-31687In 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…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-667
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jun 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 2.6.22 before 5.10.251; from 5.11 before 5.15.201; from 5.16 before 6.1.164; from 6.2 before 6.6.125; from 6.7 before 6.12.72; from 6.13 before 6.18.11; 6.19; 6.19; and 5 more ranges | NVD |
References
- https://git.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854patch
- https://git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308patch
- https://git.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54cpatch
- https://git.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50fpatch
- https://git.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687patch
- https://git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79patch
- https://git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12patch
- https://git.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435fpatch
- https://git.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25patch
- https://git.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033patch
- https://git.kernel.org/stable/c/a7fa9460b86f810913b6779461d0448e7c11214cpatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.