CVE-2026-98903: Linux kernel · mailbox: imx: Add a channel shutdown field
Source GCVE Database
Not known to be exploited · fixed in 02273054b2e94e53065ea5644265bb9d8f7ee2a7 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 02273054b2e94e53065ea5644265bb9d8f7ee2a7, 944d8509c2220a2313d4a094a646507929fb6f8d, 5ccea7eacb7786c358833634f45700365f6c1d99
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 02273054b2e94e53065ea5644265bb9d8f7ee2a7, 944d8509c2220a2313d4a094a646507929fb6f8d or 5ccea7eacb7786c358833634f45700365f6c1d99.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel by introducing a shutdown flag to properly serialize channel shutdown and interrupt event enabling. Users should update to the kernel version containing this fix once available. Patch status is not explicitly stated; check the vendor or Linux kernel advisory for the exact fixed versions and remediation guidance.
Description
A race condition vulnerability in the Linux kernel's imx mailbox driver was resolved by adding a channel shutdown field. The issue involved a timing window where the RX event could be re-enabled by an interrupt service routine while the shutdown process was waiting on free_irq(), potentially causing problems on shared interrupt handlers. This could lead to the irq-core shutting down the interrupt with a 'nobody cared' message if the removed channel triggered an interrupt.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98903 (opens in a new tab)
- git.kernel.org/stable/c/02273054b2e94e53065ea5644265bb9d8f7ee2a7 (opens in a new tab)
- git.kernel.org/stable/c/5ccea7eacb7786c358833634f45700365f6c1d99 (opens in a new tab)
- git.kernel.org/stable/c/944d8509c2220a2313d4a094a646507929fb6f8d (opens in a new tab)