CVE-2026-93085: Linux kernel · firmware: arm_scmi: Reject out of range DT protocol IDs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375, 59407ccb52130f2c81f4b3cbe4f14114afceb54f, 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 +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– |
AI-suggested
A fix has been implemented in the Linux kernel to reject out-of-range DT protocol IDs in the arm_scmi firmware component. Users should update to the fixed kernel versions containing the patches identified by the provided commit hashes to remediate this issue.
Description
A vulnerability in the Linux kernel's arm_scmi firmware component allowed out-of-range device tree (DT) protocol IDs to be processed incorrectly. The issue involved protocol IDs exceeding the allowed range being logged but still processed, leading to potential truncation or misinterpretation of protocol IDs. This could cause improper channel setup or protocol device creation. The flaw has been fixed by skipping DT protocol nodes with invalid protocol ID values during setup.
References
- git.kernel.org/stable/c/8eb2ab209570526728b35e39c4aecdb5099fbaf7 (opens in a new tab)
- git.kernel.org/stable/c/5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 (opens in a new tab)
- git.kernel.org/stable/c/e66756313d1b4eadd13f39a0aee9fc8773d4d375 (opens in a new tab)
- git.kernel.org/stable/c/0b6e59eb885f985a5ea7beed385adfa9412b324d (opens in a new tab)
- git.kernel.org/stable/c/59407ccb52130f2c81f4b3cbe4f14114afceb54f (opens in a new tab)