Memory corruption via notification teardown races
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-free in Linux 5.15 ARM SCMI notifications allows local users to trigger invalid kernel memory accesses during teardown. scmi_notification_exit() frees notification state before transport callbacks stop, while destroying notify_wq leaves init_work on the system workqueue able to dereference the same freed state. Reachability requires the affected ARM SCMI implementation and overlapping callbacks or late-init work during removal or probe-error cleanup; vendor assessments require high local privileges, and the published description establishes no reliable crash or code-execution outcome.
Summary
What happened
Use-after-free in Linux 5.15 ARM SCMI notifications allows local users to trigger invalid kernel memory accesses during teardown. scmi_notification_exit() frees notification state before transport callbacks stop, while destroying notify_wq leaves init_work on the system workqueue able to dereference the same freed state. Reachability requires the affected ARM SCMI implementation and overlapping callbacks or late-init work during removal or probe-error cleanup; vendor assessments require high local privileges, and the published description establishes no reliable crash or code-execution outcome.
The record
- CVE
- CVE-2026-93091
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1e7cbfaa66d39e78bd24df0c78b55df68176b59e <2aac23bc0a79af41104d99823bb250fae92ba144
- Affected versionversion=1e7cbfaa66d39e78bd24df0c78b55df68176b59e <5e30d3d16d1a9e599be4dcea872874e65e2c277b
- Affected versionversion=1e7cbfaa66d39e78bd24df0c78b55df68176b59e <6778bcabd2e0c32f73476f0bc6369013692540be
- Affected versionversion=1e7cbfaa66d39e78bd24df0c78b55df68176b59e <8e49055d0d495c9c07575ad8e111d9eaf0efb13f
- Affected versionversion=5.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started