CVE-2026-99189

gpio: mxc: fix race between chained IRQ handler install and probe completion

Published Oct 28, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

gpio: mxc: fix race between chained IRQ handler install and probe completion

mxc_update_irq_chained_handler() is called before the IRQ domain, the
generic IRQ chip, and the port list entry are set up. If an interrupt
arrives in that window:

- mx3_gpio_irq_handler() calls generic_handle_domain_irq() with
port->domain still NULL.
- mx2_gpio_irq_handler() walks mxc_gpio_ports, but the port has not
been added to the list yet.

Additionally, if any of the subsequent probe steps
(gpio_generic_chip_init(), devm_gpiochip_add_data(),
irq_domain_create_legacy(), or mxc_gpio_init_gc()) fail, the error
paths never unregister the chained handler, leaving a dangling handler
that points at freed memory.

Move the handler installation after all its dependencies are ready and
after list_add_tail(), so the handler is never live while the data
structures it touches are incomplete, and is never installed if probe
fails.

Analysis

AI-generated

Technical impact

In the Linux kernel, a race condition exists within the MXC GPIO driver where the chained IRQ handler is installed before the IRQ domain, generic IRQ chip, and port list are fully configured. If an interrupt occurs during this window, the handler may operate on uninitialized data such as a NULL domain pointer or a freed port structure, potentially causing a kernel panic. This vulnerability aligns with Null Pointer Dereference (CWE‑476) weaknesses.

Affected Systems

All Linux kernel implementations that include the MXC GPIO driver—commonly found in ARM‑based distributions—are potentially affected if the running kernel predates the commit that fixes the race. Based on the description, it is inferred that the driver may also be deployed on non‑ARM architectures, though the specific prevalence on other platforms is not explicitly stated.

Risk and Exploitability

The CVSS score is 4.1, indicating a low severity level, while the EPSS score of <1% suggests a very low likelihood of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. The race condition can be triggered on a system that permits manipulation of device initialization timing. Based on the description, it is inferred that an attacker could provoke interrupts during driver probe to cause a kernel crash, resulting in denial of service. Mitigation requires applying the updated kernel or the equivalent patch; otherwise, disabling or deferring the driver until the system is fully booted can reduce the risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes commit 261802c14e1a3281987ea8f106701e5ed9652f68, which removes the race condition.
  • If upgrading the kernel is not immediately possible, temporarily unbind or defer the MXC GPIO driver until after the system has completed booting to prevent early interrupts from hitting the incomplete handler.
  • Adjust the device tree or bootloader configuration to ensure MXC GPIO devices are not exposed before the driver has fully initialized, thereby eliminating the window where the race could be exploited.

Generated by OpenCVE AI on November 2, 2026 at 16:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-416
CWE-476
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: gpio: mxc: fix race between chained IRQ handler install and probe completion mxc_update_irq_chained_handler() is called before the IRQ domain, the generic IRQ chip, and the port list entry are set up. If an interrupt arrives in that window: - mx3_gpio_irq_handler() calls generic_handle_domain_irq() with port->domain still NULL. - mx2_gpio_irq_handler() walks mxc_gpio_ports, but the port has not been added to the list yet. Additionally, if any of the subsequent probe steps (gpio_generic_chip_init(), devm_gpiochip_add_data(), irq_domain_create_legacy(), or mxc_gpio_init_gc()) fail, the error paths never unregister the chained handler, leaving a dangling handler that points at freed memory. Move the handler installation after all its dependencies are ready and after list_add_tail(), so the handler is never live while the data structures it touches are incomplete, and is never installed if probe fails.
Title gpio: mxc: fix race between chained IRQ handler install and probe completion
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 28, 2026, 10:35 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 28, 2026, 11:17 AM
Severity
Moderate
Public date
Oct 28, 2026, 10:35 AM