CVE-2026-31687
In the Linux kernel, the following vulnerability has been resolved: …
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().
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854
- git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308
- git.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54c
- git.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
- git.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687
- git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79
- git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12
- git.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435f
- nvd.nist.gov/vuln/detail/CVE-2026-31687
- cve.org/CVERecord?id=CVE-2026-31687
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.