pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
Summary
| CVE | CVE-2026-92482 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:17:50 UTC |
| Updated | 2026-09-17 17:17:50 UTC |
| 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. |
Risk And Classification
EPSS: 0.001890000 probability, percentile 0.088470000 (date 2026-09-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected a6df410d420aa4ff316797d352f69e7ebae5ff98 b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b git | Not specified |
| CNA | Linux | Linux | affected a6df410d420aa4ff316797d352f69e7ebae5ff98 9c650317ba553d297f3fc5f0ae40ec53d86f9dab git | Not specified |
| CNA | Linux | Linux | affected 4.1 | Not specified |
| CNA | Linux | Linux | unaffected 4.1 semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.