firmware: arm_scmi: Publish channel state before callbacks
Summary
| CVE | CVE-2026-93093 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:03 UTC |
| Updated | 2026-10-21 13:20:59 UTC |
| 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.057850000 (date 2026-10-21)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 50e38091a657ad81385e2aea7e2575e17ac23d79 git | Not specified |
| CNA | Linux | Linux | affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 6f3f532531e4a27d28a2240719d1b05ac11766c6 git | Not specified |
| CNA | Linux | Linux | affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 1bea027f7ef6fb889628b16c568a5f7c07a51b30 git | Not specified |
| CNA | Linux | Linux | affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac a1bc587568a4e373db76261dc9561dfc3653917f git | Not specified |
| CNA | Linux | Linux | affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 0314900dcdde044af0208fed212035dbfaa55843 git | Not specified |
| CNA | Linux | Linux | affected 5.7 | Not specified |
| CNA | Linux | Linux | unaffected 5.7 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.110 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.52 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/50e38091a657ad81385e2aea7e2575e17ac23d79 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.