gpio: mxc: fix race between chained IRQ handler install and probe completion
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 261802c14e1a3281987ea8f106701e5ed9652f68, Kernel 38d44f78f041ffe60c8e2443b99434a199e7541d and Kernel 6c1e035d881579a6e4ed1ce5feabb13d23e80a82.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.6, >=5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b <261802c14e1a3281987ea8f106701e5ed9652f68, >=5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b <38d44f78f041ffe60c8e2443b99434a199e7541d, >=5f6d1998adeb5374ef248b5ba2e2a0c30ab0f60b <6c1e035d881579a6e4ed1ce5feabb13d23e80a82 | 261802c14e1a3281987ea8f106701e5ed9652f68, 38d44f78f041ffe60c8e2443b99434a199e7541d, 6c1e035d881579a6e4ed1ce5feabb13d23e80a82 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket