Unknown

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

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 Oct 23, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 02273054b2e94e53065ea5644265bb9d8f7ee2a7≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 944d8509c2220a2313d4a094a646507929fb6f8d≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5ccea7eacb7786c358833634f45700365f6c1d99< 6.12.111< 6.18.53versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 23, 2026
Affected products added · linux/linux
Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 23, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 23, 2026 · Alertas do Telegram
CVE published
Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 23, 2026 – Oct 23, 2026
1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

3 on the record

git.kernel.org/stable/c/5ccea7eacb7786c358833634f45700365f6c1d99
NIST National Vulnerability Database
git.kernel.org/stable/c/02273054b2e94e53065ea5644265bb9d8f7ee2a7
NIST National Vulnerability Database
git.kernel.org/stable/c/944d8509c2220a2313d4a094a646507929fb6f8d
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 13h
Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 13h
Unknown CVE-2026-99084 readdir: take no inode lock on an immutable directory 13h
Unknown CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 13h
Unknown CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 13h
Unknown CVE-2026-99081 bnxt_en: fix DMA mapping length for padded small packets 13h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98903 is "mailbox: imx: Add a channel shutdown field", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.