pinctrl: mediatek: free EINT resources on unbind
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e46df235b4e605aa4e7609a27c118a1cccd4ff9a · < 88292b7103d260e3e606eb3bb2794060a5fde48e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: mediatek: free EINT resources on unbind
mtk_eint_do_init() creates an IRQ domain, populates it with a mapping for every EINT line and installs a chained handler on the parent interrupt, but none of these are ever released. This was harmless while the drivers were built-in, but now that they can be built as modules and unbound/rmmod'd it leaves behind a dangling IRQ domain, interrupt mappings whose chip data points at freed memory, and a chained handler that keeps firing into that freed data.
The plain allocations in mtk_eint_do_init() already use the device-managed devm_*() helpers, so tear the remaining resources down the same way: register a devm action that detaches the chained handler, waits for any in-flight handler to finish, disposes of the per-line mappings and removes the IRQ domain. This mirrors the device-managed lifecycle adopted for the GPIO chip and keeps the whole EINT setup self-cleaning on unbind.
From the CVE record · Linux
MediaTek pinctrl EINT resources remain registered when a driver is unbound or its module is removed. A chained interrupt handler can then access freed memory; the input does not specify an attack path or authentication requirements.
Engineers running Linux kernels with MediaTek pinctrl drivers that can be unbound or removed as modules should check their installations; affected versions are not specified.