{"api_version":"1","generated_at":"2026-09-17T23:31:12+00:00","cve":"CVE-2026-93091","urls":{"html":"https://cve.report/CVE-2026-93091","api":"https://cve.report/api/cve/CVE-2026-93091.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93091","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93091"},"summary":{"title":"firmware: arm_scmi: Quiesce notifications before teardown","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Quiesce notifications before teardown\n\nscmi_notification_exit() clears and releases the notification instance,\nbut transport callbacks can still deliver incoming notifications until\nthe TX/RX channels are freed. During remove, an RX interrupt in that\nwindow can enter scmi_notify() while notification state is being torn\ndown and then dereference freed memory. The same ordering exists on the\nprobe error path after notification initialization.\n\nThe notification late-init worker has a separate lifetime issue: protocol\nevent registration queues ni->init_work on the system workqueue, so\ndestroying ni->notify_wq does not drain that work. If the devres group is\nreleased while init_work is still pending or running, the late-init worker\ncan dereference the freed notification instance.\n\nQuiesce the notification core before TX/RX channels are torn down, then\nclean up the channels before releasing the notification core resources.\nUse disable_work_sync() so future late-init queueing is rejected and any\nalready queued or running late-init work has completed before channel\nteardown starts.","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/8e49055d0d495c9c07575ad8e111d9eaf0efb13f","name":"https://git.kernel.org/stable/c/8e49055d0d495c9c07575ad8e111d9eaf0efb13f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be","name":"https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b","name":"https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144","name":"https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93091","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93091","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1e7cbfaa66d39e78bd24df0c78b55df68176b59e 6778bcabd2e0c32f73476f0bc6369013692540be git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1e7cbfaa66d39e78bd24df0c78b55df68176b59e 2aac23bc0a79af41104d99823bb250fae92ba144 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1e7cbfaa66d39e78bd24df0c78b55df68176b59e 5e30d3d16d1a9e599be4dcea872874e65e2c277b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1e7cbfaa66d39e78bd24df0c78b55df68176b59e 8e49055d0d495c9c07575ad8e111d9eaf0efb13f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15 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/notify.c","drivers/firmware/arm_scmi/notify.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"6778bcabd2e0c32f73476f0bc6369013692540be","status":"affected","version":"1e7cbfaa66d39e78bd24df0c78b55df68176b59e","versionType":"git"},{"lessThan":"2aac23bc0a79af41104d99823bb250fae92ba144","status":"affected","version":"1e7cbfaa66d39e78bd24df0c78b55df68176b59e","versionType":"git"},{"lessThan":"5e30d3d16d1a9e599be4dcea872874e65e2c277b","status":"affected","version":"1e7cbfaa66d39e78bd24df0c78b55df68176b59e","versionType":"git"},{"lessThan":"8e49055d0d495c9c07575ad8e111d9eaf0efb13f","status":"affected","version":"1e7cbfaa66d39e78bd24df0c78b55df68176b59e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/firmware/arm_scmi/driver.c","drivers/firmware/arm_scmi/notify.c","drivers/firmware/arm_scmi/notify.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.15"},{"lessThan":"5.15","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.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"5.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Quiesce notifications before teardown\n\nscmi_notification_exit() clears and releases the notification instance,\nbut transport callbacks can still deliver incoming notifications until\nthe TX/RX channels are freed. During remove, an RX interrupt in that\nwindow can enter scmi_notify() while notification state is being torn\ndown and then dereference freed memory. The same ordering exists on the\nprobe error path after notification initialization.\n\nThe notification late-init worker has a separate lifetime issue: protocol\nevent registration queues ni->init_work on the system workqueue, so\ndestroying ni->notify_wq does not drain that work. If the devres group is\nreleased while init_work is still pending or running, the late-init worker\ncan dereference the freed notification instance.\n\nQuiesce the notification core before TX/RX channels are torn down, then\nclean up the channels before releasing the notification core resources.\nUse disable_work_sync() so future late-init queueing is rejected and any\nalready queued or running late-init work has completed before channel\nteardown starts."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:11:07.055Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be"},{"url":"https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144"},{"url":"https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b"},{"url":"https://git.kernel.org/stable/c/8e49055d0d495c9c07575ad8e111d9eaf0efb13f"}],"title":"firmware: arm_scmi: Quiesce notifications before teardown","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93091","datePublished":"2026-09-17T16:11:07.055Z","dateReserved":"2026-09-17T16:02:15.084Z","dateUpdated":"2026-09-17T16:11:07.055Z","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":"93091","Ordinal":"1","Title":"firmware: arm_scmi: Quiesce notifications before teardown","CVE":"CVE-2026-93091","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93091","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Quiesce notifications before teardown\n\nscmi_notification_exit() clears and releases the notification instance,\nbut transport callbacks can still deliver incoming notifications until\nthe TX/RX channels are freed. During remove, an RX interrupt in that\nwindow can enter scmi_notify() while notification state is being torn\ndown and then dereference freed memory. The same ordering exists on the\nprobe error path after notification initialization.\n\nThe notification late-init worker has a separate lifetime issue: protocol\nevent registration queues ni->init_work on the system workqueue, so\ndestroying ni->notify_wq does not drain that work. If the devres group is\nreleased while init_work is still pending or running, the late-init worker\ncan dereference the freed notification instance.\n\nQuiesce the notification core before TX/RX channels are torn down, then\nclean up the channels before releasing the notification core resources.\nUse disable_work_sync() so future late-init queueing is rejected and any\nalready queued or running late-init work has completed before channel\nteardown starts.","Type":"Description","Title":"firmware: arm_scmi: Quiesce notifications before teardown"}]}}}