VulnerabilityPublished 28 Oct 2026

CVE-2026-99189: Linux kernel · gpio: mxc: fix race between chained IRQ handler install and probe completion

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 261802c14e1a3281987ea8f106701e5ed9652f68 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 261802c14e1a3281987ea8f106701e5ed9652f68, 38d44f78f041ffe60c8e2443b99434a199e7541d, 6c1e035d881579a6e4ed1ce5feabb13d23e80a82

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 261802c14e1a3281987ea8f106701e5ed9652f68, 38d44f78f041ffe60c8e2443b99434a199e7541d or 6c1e035d881579a6e4ed1ce5feabb13d23e80a82.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b, < 261802c14e1a3281987ea8f106701e5ed9652f68	Fixed in 261802c14e1a3281987ea8f106701e5ed9652f68
LinuxLinux	Affected ≥ 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b, < 38d44f78f041ffe60c8e2443b99434a199e7541d	Fixed in 38d44f78f041ffe60c8e2443b99434a199e7541d
LinuxLinux	Affected ≥ 5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b, < 6c1e035d881579a6e4ed1ce5feabb13d23e80a82	Fixed in 6c1e035d881579a6e4ed1ce5feabb13d23e80a82
LinuxLinux	Affected =6.6	Fixed in–

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.

References

Community reviews

Loading reviews…