CVE-2026-31687

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().

Gravité et risque d'exploitation

CVE-2026-31687 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.5 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <57bcd3feffa79544c73a1a1872472389a391cc79, <=6.1.*, <=6.12.*, 5.15.201, 6.1.164, 6.19.1, 0, <32f08c3ddd6dda6cbb6c9d715de10f21dccde50f, <730e5ebff40c852e3ea57b71bf02a4b89c69435f, <6.12.73, <673dafb9a86349a12a93151fd467625614dc7e12, <6.19.2, 8d76b2488eb3cc0717ab81b60622cff4a5f90f79, <=5.10.*, <=6.6.*, <53a76425e0764421ba93bb9045d2e454667d5687, <=6.19.*, <6.18.12, 6.18.12, 6.6.125, <03db4dc9ad6eb91e640b517e00373ce877682854, <=6.18.*, 6.6.126, 11a78b7944963a8b052be46108d07a3ced9e2762, 6.12.72, <6.6.126, 2.6.22, <2.6.22, adc1796eced46b48e23ec200a219d635f33a38ee, <2211d77892913804d16c28c7415b82804ab1e54c, <=*, <=5.15.*, 6.19, 6.19.2, <a29215961d833f4de33a09c3964d31ebc6083033, 6.18.11, 6.12.73, cd0e0a76e40c2e77bcfc88291d00dca22b00158e, <86588916e1887a5edb8a9161cd7ae81e47a7ed25, bc82e5f4d7dc8237ae8cabc73aa46fc93c85d98c, <1c04c3a4de8d4bcb9202f94c44f26c57c2572308, <a7fa9460b86f810913b6779461d0448e7c11214c, 5.10.251) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79
• https://git.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25
• https://git.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033
• https://git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308
• https://git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12
• https://git.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54c
• https://git.kernel.org/stable/c/a7fa9460b86f810913b6779461d0448e7c11214c
• https://git.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
• https://git.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687
• https://git.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435f
• https://git.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854