Strix
63.2K

CVE-2026-92481

Unknown

Last modified

CVE-2026-92481 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < 23252bc1cd9a58a039c9b1ae77b22d2b33da48e9; >= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < 903a7cdf63a81d3738594c5bd1b5955f58fda427; >= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < 51552c8c60d3b1fecc062eab2d8cfeaa1cb339dd; >= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < 7f6d898179ca4771ee602bdad4246c3952af83eb; >= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < e06785cba7f86d72abd531058b1a82d6952a7346; >= e46df235b4e605aa4e7609a27c118a1cccd4ff9a, < 88292b7103d260e3e606eb3bb2794060a5fde48e
LinuxLinux4.18

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-92481?
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.
How severe is CVE-2026-92481?
Severity scoring for CVE-2026-92481 is pending analysis.
How do I fix CVE-2026-92481?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-92481?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST