Answer in brief
CVE-2026-93093 records a Unknown severity vulnerability in firmware: arm_scmi: Publish channel state before callbacks. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <6f3f532531e4a27d28a2240719d1b05ac11766c6 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <1bea027f7ef6fb889628b16c568a5f7c07a51b30 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <a1bc587568a4e373db76261dc9561dfc3653917f || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <0314900dcdde044af0208fed212035dbfaa55843 | 6f3f532531e4a27d28a2240719d1b05ac11766c6, 1bea027f7ef6fb889628b16c568a5f7c07a51b30, a1bc587568a4e373db76261dc9561dfc3653917f, 0314900dcdde044af0208fed212035dbfaa55843 |
| Linux/Linuxgeneric | 5.7 | Not reported |
| Linux/Linuxgeneric | >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <50e38091a657ad81385e2aea7e2575e17ac23d79 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <6f3f532531e4a27d28a2240719d1b05ac11766c6 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <1bea027f7ef6fb889628b16c568a5f7c07a51b30 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <a1bc587568a4e373db76261dc9561dfc3653917f || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <0314900dcdde044af0208fed212035dbfaa55843 | 50e38091a657ad81385e2aea7e2575e17ac23d79, 6f3f532531e4a27d28a2240719d1b05ac11766c6, 1bea027f7ef6fb889628b16c568a5f7c07a51b30, a1bc587568a4e373db76261dc9561dfc3653917f, 0314900dcdde044af0208fed212035dbfaa55843 |
| Linux/Linuxgeneric | >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <9d349c7b2392b1196e10421421ea9a09fcc5d3cc || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <50e38091a657ad81385e2aea7e2575e17ac23d79 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <6f3f532531e4a27d28a2240719d1b05ac11766c6 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <1bea027f7ef6fb889628b16c568a5f7c07a51b30 || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <a1bc587568a4e373db76261dc9561dfc3653917f || >=5c8a47a5a91d4d6e185f758d61997613d9c5d6ac <0314900dcdde044af0208fed212035dbfaa55843 | 9d349c7b2392b1196e10421421ea9a09fcc5d3cc, 50e38091a657ad81385e2aea7e2575e17ac23d79, 6f3f532531e4a27d28a2240719d1b05ac11766c6, 1bea027f7ef6fb889628b16c568a5f7c07a51b30, a1bc587568a4e373db76261dc9561dfc3653917f, 0314900dcdde044af0208fed212035dbfaa55843 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.