gpio: omap: do not register driver in probe()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 11a78b7944963a8b052be46108d07a3ced9e2762 · < 2211d77892913804d16c28c7415b82804ab1e54c| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel’s OMAP GPIO code registers a driver during a probe callback, which can cause a deadlock when a device lock is held. The description does not specify how an attacker could trigger it or whether access or user interaction is required.
Engineers running Linux kernels with the OMAP GPIO driver should check their kernel version; affected versions are not specified.