- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Publish channel state before callbacks Transport setup can enable callbacks before the setup routine returns. mailbox_chan_setup() registers the mailbox client with mbox_request_channel(), and the mailbox controller startup path can enable interrupt delivery before SCMI mailbox channel state has been published. Similarly, smc_chan_setup() requests the optional A2P completion IRQ before the SMC transport has made its cinfo pointer visible. If a pending or spurious callback fires in those windows, the transport RX callback can dereference a NULL transport cinfo pointer. Publishing only the transport-private pointer is not sufficient either: an early callback can enter the SCMI core before scmi_chan_setup() has assigned cinfo->handle. The core derives scmi_info from cinfo->handle in the RX path, so a NULL handle can still fault even when the transport-private cinfo is valid. Assign cinfo->handle before invoking the transport setup callback. Publish the mailbox and SMC transport-private channel state before requesting the mailbox channels or IRQ, and clear the early-published pointers again on setup failure. Also unwind mailbox setup devres resources on failure so an optional RX setup error that is ignored by the core does not leave stale transport state behind.
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 9d349c7b2392b1196e10421421ea9a09fcc5d3cc
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 50e38091a657ad81385e2aea7e2575e17ac23d79
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 6f3f532531e4a27d28a2240719d1b05ac11766c6
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 1bea027f7ef6fb889628b16c568a5f7c07a51b30
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < a1bc587568a4e373db76261dc9561dfc3653917f
- affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 0314900dcdde044af0208fed212035dbfaa55843
- affected 5.7
- unaffected < 5.7
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/9d349c7b2392b1196e10421421ea9a09fcc5d3cc (opens in a new tab)
- https://git.kernel.org/stable/c/50e38091a657ad81385e2aea7e2575e17ac23d79 (opens in a new tab)
- https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6 (opens in a new tab)
- https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30 (opens in a new tab)
- https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f (opens in a new tab)
- https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82201 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93093)Record last updated .