{"api_version":"1","generated_at":"2026-09-17T23:31:14+00:00","cve":"CVE-2026-93093","urls":{"html":"https://cve.report/CVE-2026-93093","api":"https://cve.report/api/cve/CVE-2026-93093.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93093","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93093"},"summary":{"title":"firmware: arm_scmi: Publish channel state before callbacks","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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:18:03","updated_at":"2026-09-17 17:18:03"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30","name":"https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843","name":"https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f","name":"https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6","name":"https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93093","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93093","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 6f3f532531e4a27d28a2240719d1b05ac11766c6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 1bea027f7ef6fb889628b16c568a5f7c07a51b30 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac a1bc587568a4e373db76261dc9561dfc3653917f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac 0314900dcdde044af0208fed212035dbfaa55843 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/firmware/arm_scmi/driver.c","drivers/firmware/arm_scmi/transports/mailbox.c","drivers/firmware/arm_scmi/transports/smc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"6f3f532531e4a27d28a2240719d1b05ac11766c6","status":"affected","version":"5c8a47a5a91d4d6e185f758d61997613d9c5d6ac","versionType":"git"},{"lessThan":"1bea027f7ef6fb889628b16c568a5f7c07a51b30","status":"affected","version":"5c8a47a5a91d4d6e185f758d61997613d9c5d6ac","versionType":"git"},{"lessThan":"a1bc587568a4e373db76261dc9561dfc3653917f","status":"affected","version":"5c8a47a5a91d4d6e185f758d61997613d9c5d6ac","versionType":"git"},{"lessThan":"0314900dcdde044af0208fed212035dbfaa55843","status":"affected","version":"5c8a47a5a91d4d6e185f758d61997613d9c5d6ac","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/firmware/arm_scmi/driver.c","drivers/firmware/arm_scmi/transports/mailbox.c","drivers/firmware/arm_scmi/transports/smc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.7"},{"lessThan":"5.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","versionStartIncluding":"5.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"5.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"5.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"5.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:11:08.360Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/6f3f532531e4a27d28a2240719d1b05ac11766c6"},{"url":"https://git.kernel.org/stable/c/1bea027f7ef6fb889628b16c568a5f7c07a51b30"},{"url":"https://git.kernel.org/stable/c/a1bc587568a4e373db76261dc9561dfc3653917f"},{"url":"https://git.kernel.org/stable/c/0314900dcdde044af0208fed212035dbfaa55843"}],"title":"firmware: arm_scmi: Publish channel state before callbacks","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93093","datePublished":"2026-09-17T16:11:08.360Z","dateReserved":"2026-09-17T16:02:15.084Z","dateUpdated":"2026-09-17T16:11:08.360Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:18:03","lastModifiedDate":"2026-09-17 17:18:03","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93093","Ordinal":"1","Title":"firmware: arm_scmi: Publish channel state before callbacks","CVE":"CVE-2026-93093","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93093","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"firmware: arm_scmi: Publish channel state before callbacks"}]}}}