Vulnerability 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.
References
- https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab
- https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b
FAQ
What is CVE-2026-92482?
CVE-2026-92482 is a documented vulnerability. 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...
How severe is CVE-2026-92482?
CVSS scoring is not yet available for CVE-2026-92482. Check NVD for updates.
Is there a patch for CVE-2026-92482?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.