CVE-2026-31687
Published: Apr 27, 2026
Modified: May 23, 2026
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().
| Vendor | Product | Versions |
|---|---|---|
Linux | Linux | affected 11a78b7944963a8b052be46108d07a3ced9e2762 - < 57bcd3feffa79544c73a1a1872472389a391cc79affected 11a78b7944963a8b052be46108d07a3ced9e2762 - < 86588916e1887a5edb8a9161cd7ae81e47a7ed25affected 11a78b7944963a8b052be46108d07a3ced9e2762 - < a29215961d833f4de33a09c3964d31ebc6083033affected 11a78b7944963a8b052be46108d07a3ced9e2762 - < 1c04c3a4de8d4bcb9202f94c44f26c57c2572308affected adc1796eced46b48e23ec200a219d635f33a38ee - < 673dafb9a86349a12a93151fd467625614dc7e12+10 more versions |
Linux | Linux | affected 2.6.22unaffected 0 - < 2.6.22unaffected 5.10.251 - <= 5.10.*unaffected 5.15.201 - <= 5.15.*unaffected 6.1.164 - <= 6.1.*+8 more versions |
References
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now