CVE-2026-92482: Linux kernel · pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dc6e5d802c88468290fee8826dd3a54cf58da25a : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in dc6e5d802c88468290fee8826dd3a54cf58da25a, b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b, 2490528a90a26f408ec3e95f865bad35454f9ff3 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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
- git.kernel.org/stable/c/dc6e5d802c88468290fee8826dd3a54cf58da25a (opens in a new tab)
- git.kernel.org/stable/c/2490528a90a26f408ec3e95f865bad35454f9ff3 (opens in a new tab)
- git.kernel.org/stable/c/01b5fcdc30c0ab35af960b60508eae1f7f7d32fd (opens in a new tab)
- git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b (opens in a new tab)
- git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab (opens in a new tab)