# CVE-2026-92482: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

> A use-after-free in the MediaTek pinctrl driver allows local attackers with module loading privileges to execute arbitrary code or escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110441, BELL-CVE-2026-92482, DEBIAN-CVE-2026-92482, GHSA-6wqp-4g53-5h3x, UBUNTU-CVE-2026-92482

## What is CVE-2026-92482?

CVE-2026-92482 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-92482?


## How do I fix CVE-2026-92482?

Apply the vendor's patch.

## Is CVE-2026-92482 being exploited?

There is no known exploitation of CVE-2026-92482 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92482 and fix it if it is affected.

What it is: CVE-2026-92482 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92482 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92482/ (Markdown: https://insights.sbomify.com/CVE-2026-92482/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92482
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92482
- OSV: https://osv.dev/vulnerability/CVE-2026-92482

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92482/
Summaries are generated and may contain mistakes; the official description above is the record.