Description
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.
Metrics
No CVSS score has been published yet.
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < 13a25cb4f0f0863afded5e915cb3bceede221426; >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < dc6e5d802c88468290fee8826dd3a54cf58da25a; >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < 2490528a90a26f408ec3e95f865bad35454f9ff3; >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < 01b5fcdc30c0ab35af960b60508eae1f7f7d32fd; >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b; >= a6df410d420aa4ff316797d352f69e7ebae5ff98, < 9c650317ba553d297f3fc5f0ae40ec53d86f9dab |
| Linux | Linux | 4.1 |
References
- https://git.kernel.org/stable/c/01b5fcdc30c0ab35af960b60508eae1f7f7d32fd
- https://git.kernel.org/stable/c/13a25cb4f0f0863afded5e915cb3bceede221426
- https://git.kernel.org/stable/c/2490528a90a26f408ec3e95f865bad35454f9ff3
- https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab
- https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b
- https://git.kernel.org/stable/c/dc6e5d802c88468290fee8826dd3a54cf58da25a
Timeline
- Published
- Sep 17, 2026
- Last modified
- Oct 30, 2026
- NVD status
- Received