CVE-2026-93091

firmware: arm_scmi: Quiesce notifications before teardown

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Quiesce notifications before teardown scmi_notification_exit() clears and releases the notification instance, but transport callbacks can still deliver incoming notifications until the TX/RX channels are freed. During remove, an RX interrupt in that window can enter scmi_notify() while notification state is being torn down and then dereference freed memory. The same ordering exists on the probe error path after notification initialization. The notification late-init worker has a separate lifetime issue: protocol event registration queues ni->init_work on the system workqueue, so destroying ni->notify_wq does not drain that work. If the devres group is released while init_work is still pending or running, the late-init worker can dereference the freed notification instance. Quiesce the notification core before TX/RX channels are torn down, then clean up the channels before releasing the notification core resources. Use disable_work_sync() so future late-init queueing is rejected and any already queued or running late-init work has completed before channel teardown starts.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1e7cbfaa66d39e78bd24df0c78b55df68176b59e5.15
Vendor states this is fixed in 2aac23bc0a79af41104d99823bb250fae92ba144 (fixed)
Vendor states this is fixed in 5e30d3d16d1a9e599be4dcea872874e65e2c277b (fixed)
Vendor states this is fixed in 6778bcabd2e0c32f73476f0bc6369013692540be (fixed)
Vendor states this is fixed in 8e49055d0d495c9c07575ad8e111d9eaf0efb13f (fixed)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card