{"identifier":"CVE-2026-93093","cve":{"id":"CVE-2026-93093","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Publish channel state before callbacks\n\nTransport setup can enable callbacks before the setup routine returns.\nmailbox_chan_setup() registers the mailbox client with\nmbox_request_channel(), and the mailbox controller startup path can enable\ninterrupt delivery before SCMI mailbox channel state has been published.\nSimilarly, smc_chan_setup() requests the optional A2P completion IRQ before\nthe SMC transport has made its cinfo pointer visible.\n\nIf a pending or spurious callback fires in those windows, the transport RX\ncallback can dereference a NULL transport cinfo pointer. Publishing only\nthe transport-private pointer is not sufficient either: an early callback\ncan enter the SCMI core before scmi_chan_setup() has assigned\ncinfo->handle.\nThe core derives scmi_info from cinfo->handle in the RX path, so a NULL\nhandle can still fault even when the transport-private cinfo is valid.\n\nAssign cinfo->handle before invoking the transport setup callback. Publish\nthe mailbox and SMC transport-private channel state before requesting the\nmailbox channels or IRQ, and clear the early-published pointers again on\nsetup failure. Also unwind mailbox setup devres resources on failure so an\noptional RX setup error that is ignored by the core does not leave stale\ntransport state behind.","published":"2026-09-17T17:18:03.300000+00:00","modified":"2026-10-30T13:20:57.117000+00:00","status":"Received","score":null,"severity":"UNSCORED","vector":"","cvss_version":"","affected":[],"weaknesses":[],"references":[{"url":"https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/50e38091a657ad81385e2aea7e2575e17ac23d79","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/9d349c7b2392b1196e10421421ea9a09fcc5d3cc","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"kev":null,"kev_checked":true,"metrics":{},"configurations":[],"source":"nvd","retrieved_at":"2026-10-30T15:50:58.257770+00:00","exploited":false,"kev_stale":false,"products":[],"priority":{"label":"Assess exposure and vendor guidance","reasons":["No higher-priority signal is available in the current stored evidence."]},"epss":{"probability":0.00173,"percentile":0.06849,"date":"2026-11-18","stale":false},"version_assessment":null},"news":[],"campaigns":[],"domains":[{"domain":"git.kernel.org","source_url":"https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843","investigate_url":"https://investigate.aeglixmind.com/#git.kernel.org"}],"arsenal_url":"https://arsenal.aeglixmind.com/?cve=CVE-2026-93093","catalog_url":"https://cves.aeglixmind.com/cve/CVE-2026-93093","research_url":"https://investigate.aeglixmind.com/research/cve/CVE-2026-93093","coverage":{"news_candidates_checked":0,"campaign_candidates_checked":0,"bounded":false,"notice":"Exact CVE mentions in stored public excerpts and reviewed campaign content only. A mention is not proof of exploitation, attribution or tool suitability. Missing matches do not establish absence."}}