CVE-2026-31687

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gpio: omap: do not register driver in probe()<br /> <br /> Commit 11a78b794496 ("ARM: OMAP: MPUIO wake updates") registers the<br /> omap_mpuio_driver from omap_mpuio_init(), which is called from<br /> omap_gpio_probe().<br /> <br /> However, it neither makes sense to register drivers from probe()<br /> callbacks of other drivers, nor does the driver core allow registering<br /> drivers with a device lock already being held.<br /> <br /> The latter was revealed by commit dc23806a7c47 ("driver core: enforce<br /> device_lock for driver_match_device()") leading to a potential deadlock<br /> condition described in [1].<br /> <br /> Additionally, the omap_mpuio_driver is never unregistered from the<br /> driver core, even if the module is unloaded.<br /> <br /> Hence, register the omap_mpuio_driver from the module initcall and<br /> unregister it in module_exit().