Kernel memory corruption via SCMI removal race
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-free in Linux 6.3 SCMI device removal allows local users to corrupt kernel memory via concurrent driver unregisters. In scmi_protocol_device_unrequest(), releasing scmi_requested_devices_mtx during notification leaves a retained list head exposed to another unregister operation, causing a freed-pointer dereference and double free. Triggering the race requires concurrent removal of two SCMI drivers for the same protocol; Amazon's assessment requires administrative privileges, and the upstream notice does not establish arbitrary code execution.
Summary
What happened
Use-after-free in Linux 6.3 SCMI device removal allows local users to corrupt kernel memory via concurrent driver unregisters. In scmi_protocol_device_unrequest(), releasing scmi_requested_devices_mtx during notification leaves a retained list head exposed to another unregister operation, causing a freed-pointer dereference and double free. Triggering the race requires concurrent removal of two SCMI drivers for the same protocol; Amazon's assessment requires administrative privileges, and the upstream notice does not establish arbitrary code execution.
The record
- CVE
- CVE-2026-92506
- 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=6.3
- Affected versionversion=d3cd7c525fd2ecce3a6c963f314969a54783d211 <1c35915eaaa81a12340c838c5c2ccb02be2194c3
- Affected versionversion=d3cd7c525fd2ecce3a6c963f314969a54783d211 <21d35c5f46e99e9047bb9ded3ecb5ab440dd75b3
- Affected versionversion=d3cd7c525fd2ecce3a6c963f314969a54783d211 <2c4097e6c4aed276c5e9ec2ab331ab397ea780bf
- Affected versionversion=d3cd7c525fd2ecce3a6c963f314969a54783d211 <2ff7713b7308cd6bea3328f7cd750b5eaab42af3
- Affected versionversion=d3cd7c525fd2ecce3a6c963f314969a54783d211 <c3d4ef1c0ca6917aad6f1093b49f3932944a8c19
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