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.
Published: 2026-10-23
Score: n/a
EPSS: n/a
KEV: No
Impact: Race Condition Causing Kernel Interrupt Issues
Action: Apply Patch
AI Analysis

Impact

The Linux kernel’s imx mailbox driver contains a race between channel shutdown and the interrupt service routine, allowing an interrupt event to remain enabled after the channel is removed. This flaw can cause unexpected interrupt handling and potentially lead to a kernel crash or denial of service. The vulnerability is a concurrency fault and does not directly enable code execution.

Affected Systems

This flaw exists in any Linux kernel build that includes the imx mailbox subsystem, typically used on i.MX System-on-Chip platforms. Because specific affected kernel versions are not listed, any build of the kernel before the upstream fix that employs the vulnerable mailbox driver may be impacted.

Risk and Exploitability

The race condition requires precise timing and access to the same interrupt handler, making it difficult to trigger from user space. No EPSS score is available and the vulnerability is not listed in CISA KEV, indicating moderate or lower exploitation likelihood. While it does not provide remote code execution, an attacker could use the flaw to destabilize the system. Applying the official patch that introduces the shutdown flag removes the race and prevents the problematic interrupt behavior.

Generated by OpenCVE AI on October 23, 2026 at 14:46 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor’s kernel patch that adds the shutdown flag to the imx mailbox driver.
  • Reboot the system after patching to ensure the new driver code is loaded and the IRQ handler is reset.
  • If an immediate kernel upgrade is not feasible, disable the imx mailbox device or its interrupt source until the patch can be applied.

Generated by OpenCVE AI on October 23, 2026 at 14:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 23 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Fri, 23 Oct 2026 15:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Fri, 23 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
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.
Title mailbox: imx: Add a channel shutdown field
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-23T11:54:15.010Z

Reserved: 2026-09-25T10:25:14.379Z

Link: CVE-2026-98903

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-23T12:18:24.370

Modified: 2026-10-23T12:18:24.370

Link: CVE-2026-98903

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T15:15:14Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')