pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a6df410d420aa4ff316797d352f69e7ebae5ff98 · < 9c650317ba553d297f3fc5f0ae40ec53d86f9dab| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free.
Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.
From the CVE record · Linux
The MediaTek pinctrl driver registers a device-managed GPIO chip without tying its registration to the same lifecycle. When the driver is built as a module and unbound or removed, the chip's memory can be freed while it remains registered, causing a use-after-free. The input does not specify an attacker action, authentication requirement, or user interaction.
Engineers running Linux kernels with the MediaTek pinctrl driver built as a module should check their kernel; affected versions are not specified.