mailbox: imx: Add a channel shutdown field
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.111, 6.18.53
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Linux kernel's i.MX mailbox driver (mailbox: imx) is affected, where a race during channel teardown can leave a receive interrupt enabled after shutdown. On systems with shared interrupt handlers, this could cause the kernel to log "nobody cared" interrupt messages and disable the interrupt line.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In the Linux kernel, the following vulnerability has been resolved: mailbox: imx: Add a channel shutdown field sashiko complained about possible teardown problem. The scenario CPU 0 CPU 1 imx_mu_isr() imx_mu_shutdown() imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv->dcfg->type, cp->idx)); imx_mu_specific_rx() imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv->dcfg->type, 0), 0); free_irq() The RX event remains enabled because in this short window the RX event was disabled in ->shutdown() while the interrupt was active and then enabled again by the ISR while ->shutdown waited in free_irq(). This race requires timing and if happens can be problematic on shared handlers if the "removed" channel triggers an interrupt. In this case the irq-core will shutdown the interrupt with the "nobody cared" message. Introduce imx_mu_con_priv::shutdown to signal that the channel is shutting down. This flag is set with the lock held (by imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which only enables the event if the channel has not been shutdown and serialises on the same lock.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Linux
From 0a67003b1985c79811160af1b01aca07cd5fbc53 · fixed in 02273054b2e94e53065ea5644265bb9d8f7ee2a7; From 0a67003b1985c79811160af1b01aca07cd5fbc53 · fixed in 944d8509c2220a2313d4a094a646507929fb6f8d; From 0a67003b1985c79811160af1b01aca07cd5fbc53 · fixed in 5ccea7eacb7786c358833634f45700365f6c1d99
- Linux Linux
5.7
- KernelLinux
fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53