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: 4.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel Interrupt Race Condition
Action: Apply Patch
AI Analysis

Impact

The Linux kernel’s imx mailbox driver contains a race condition (CWE-366) between a channel shutdown routine and its interrupt service routine. If an interrupt occurs while a channel is being shut down, the receive event may remain enabled, allowing the interrupt core to shut down a channel that has already been requested for removal. This flaw can produce a "nobody cared" error and, in rare corner cases, trigger a kernel panic, leading to local denial of service without providing remote code execution. The vulnerability hinges on precise timing and proper synchronization, making it a low‑severity concurrency bug.

Affected Systems

This defect exists in any Linux kernel build that includes the imx mailbox subsystem, which is used on i.MX System‑on‑Chip platforms such as the i.MX6, i.MX7, and i.MX8 families. Because the CVE documentation does not specify a version range, all kernel releases prior to the upstream fix that ship the vulnerable driver code are potentially affected. No vendor‑specific restricted product lists are provided.

Risk and Exploitability

The CVSS score of 4.1 indicates low severity. The EPSS score is less than 1 %, indicating a very low probability of exploitation. The vulnerability is not listed in the CISA KEV database, meaning there are no known exploit campaigns. The race requires careful timing and control of interrupts, so it is unlikely to be exploitable from user space without root privileges. Nevertheless, the effect can lead to kernel instability, so patching is recommended.

Generated by OpenCVE AI on October 27, 2026 at 11:35 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel patch that introduces the shutdown flag and synchronizes channel access in the imx mailbox driver.
  • Reboot the system after installing the patch to force the driver to reinitialize and clear any stale interrupt state.
  • If a kernel update is not possible immediately, temporarily disable the imx mailbox device or block its interrupts to prevent the race from occurring.

Generated by OpenCVE AI on October 27, 2026 at 11:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
History

Tue, 27 Oct 2026 09:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Tue, 27 Oct 2026 04:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-366
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


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-26T06:56:31.630Z

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-26T07:17:15.670

Link: CVE-2026-98903

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-23T00:00:00Z

Links: CVE-2026-98903 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-27T11:45:13Z

Weaknesses
  • CWE-366

    Race Condition within a Thread