VYPR
Medium severity5.5NVD Advisory· Published Apr 27, 2026· Updated May 6, 2026

CVE-2026-31687

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

Affected products

9
  • Torvalds/Linuxinferred
  • Linux/Kernel8 versions
    cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*+ 7 more
    • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*range: >=2.6.22,<5.10.251
    • cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

News mentions

0

No linked articles in our index yet.