# CVE-2026-92481: pinctrl: mediatek: free EINT resources on unbind

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

- **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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-92481, DEBIAN-CVE-2026-92481, GHSA-fmh8-wm6j-9mrf, UBUNTU-CVE-2026-92481

## What is CVE-2026-92481?

CVE-2026-92481 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: free EINT resources on unbind

mtk_eint_do_init() creates an IRQ domain, populates it with a mapping for
every EINT line and installs a chained handler on the parent interrupt,
but none of these are ever released. This was harmless while the drivers
were built-in, but now that they can be built as modules and
unbound/rmmod'd it leaves behind a dangling IRQ domain, interrupt mappings
whose chip data points at freed memory, and a chained handler that keeps
firing into that freed data.

The plain allocations in mtk_eint_do_init() already use the device-managed
devm_*() helpers, so tear the remaining resources down the same way:
register a devm action that detaches the chained handler, waits for any
in-flight handler to finish, disposes of the per-line mappings and removes
the IRQ domain. This mirrors the device-managed lifecycle adopted for the
GPIO chip and keeps the whole EINT setup self-cleaning on unbind.

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


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

Apply the vendor's patch.

## Is CVE-2026-92481 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92481 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-92481 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-92481/ (Markdown: https://insights.sbomify.com/CVE-2026-92481/index.md)
```

## Sources

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

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