CVE-2026-93085 — firmware: arm_scmi: Reject out of range DT protocol IDs
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Reject out of range DT protocol IDs SCMI protocol IDs carried in message headers are limited by MSG_PROTOCOL_ID_MASK. The DT parsing paths noticed protocol IDs outside that range, but only logged an error and then kept processing the invalid value. That lets a malformed 32-bit DT reg value reach helpers which take a u8 protocol ID, where it can be truncated and/or treated as a different protocol. For channel setup, two different out-of-range values can also be used as distinct IDR keys while aliasing the generated SCMI protocol identity. Skip DT protocol nodes whose reg value does not fit the SCMI protocol ID field before setting up channels or creating protocol devices.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and < 8eb2ab209570526728b35e39c4aecdb5099fbaf7≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and < 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and < e66756313d1b4eadd13f39a0aee9fc8773d4d375≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and < 0b6e59eb885f985a5ea7beed385adfa9412b324d≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 and < 59407ccb52130f2c81f4b3cbe4f14114afceb54fversion 6.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
5 on the record
- git.kernel.org/stable/c/8eb2ab209570526728b35e39c4aecdb5099fbaf7
- git.kernel.org/stable/c/59407ccb52130f2c81f4b3cbe4f14114afceb54f
- git.kernel.org/stable/c/0b6e59eb885f985a5ea7beed385adfa9412b324d
- git.kernel.org/stable/c/5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1
- git.kernel.org/stable/c/e66756313d1b4eadd13f39a0aee9fc8773d4d375
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 6h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 6h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 6h
- Unknown CVE-2026-98861 fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching() 6h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 6h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 6h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93085 is "firmware: arm_scmi: Reject out of range DT protocol IDs", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.