CVE-2026-99189: gpio: mxc: fix race between chained IRQ handler install and probe completion
gpio: mxc: fix race between chained IRQ handler install and probe completion
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.59 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.13 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 7.2.15-1Fixed in 7.3.3-1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Compensating control
In the Linux kernel gpio-mxc probe path, install the chained IRQ handler with mxc_update_irq_chained_handler() only after the IRQ domain, generic IRQ chip, and port list entry have been initialized, including after list_add_tail(), so it is not active during incomplete probe or failure cleanup.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel mxc GPIO driver are exposed during driver probing if an interrupt can arrive before the driver has finished creating its IRQ domain, generic IRQ chip, and port-list entry. The issue also applies when later probe steps fail after a chained IRQ handler has been installed.
What conditions are needed to trigger the race?
An interrupt must arrive in the short interval after the chained IRQ handler is installed but before its required GPIO and IRQ data structures are ready. On the mx3 handler path, this can invoke domain IRQ handling with a NULL domain; on the mx2 path, the handler can run before the port is present in the global port list.
What is the impact of a probe failure after handler installation?
If GPIO or IRQ initialization fails after the handler is installed, the prior error paths do not unregister that handler. It can remain registered with a pointer to freed memory, creating a dangling handler.
What does the fix change?
The fix delays chained IRQ handler installation until the IRQ dependencies are initialized and the port has been added to the list. This prevents the handler from becoming live during incomplete initialization and avoids installing it when probing fails.