CVE-2026-92506: Linux kernel · firmware: arm_scmi: Fix requested device removal race
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c3d4ef1c0ca6917aad6f1093b49f3932944a8c19 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c3d4ef1c0ca6917aad6f1093b49f3932944a8c19, 21d35c5f46e99e9047bb9ded3ecb5ab440dd75b3, 2ff7713b7308cd6bea3328f7cd750b5eaab42af3 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix requested device removal race scmi_protocol_device_unrequest() drops scmi_requested_devices_mtx while notifying listeners but continues to retain the per-protocol list head. When two SCMI drivers for the same protocol unregister concurrently, one thread can remove the final request and free the list head while the other is running its notifier. The latter then dereferences the freed list head after reacquiring the mutex and can free it a second time. Complete the list and IDR updates, including freeing an empty list head, before dropping the mutex. Keep the blocking notifier outside the critical section and retain only the detached request across the callback.
References
- git.kernel.org/stable/c/2ff7713b7308cd6bea3328f7cd750b5eaab42af3 (opens in a new tab)
- git.kernel.org/stable/c/1c35915eaaa81a12340c838c5c2ccb02be2194c3 (opens in a new tab)
- git.kernel.org/stable/c/c3d4ef1c0ca6917aad6f1093b49f3932944a8c19 (opens in a new tab)
- git.kernel.org/stable/c/21d35c5f46e99e9047bb9ded3ecb5ab440dd75b3 (opens in a new tab)
- git.kernel.org/stable/c/2c4097e6c4aed276c5e9ec2ab331ab397ea780bf (opens in a new tab)