# firmware: arm_scmi: Reject out of range DT protocol IDs CVE record · `CVE-2026-93085` - **Identifiers:** `CVE-2026-93085` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **CNA:** Linux - **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md) - **Published:** 17 Sept 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the CVE Program (CNA: Linux) at 17 Sept 2026, 16:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. ## Affected products, as the CNA wrote them - Vendor: Linux. Product: Linux. - affected: `22f7f35fd71b597a5d916e41d7646be6ee530c86 to before 75d6273a28cdb543a167ac5fbfca75dc286ffe10` (git) - affected: `05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 to before 8eb2ab209570526728b35e39c4aecdb5099fbaf7` (git) - affected: `05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 to before 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1` (git) - affected: `05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 to before e66756313d1b4eadd13f39a0aee9fc8773d4d375` (git) - affected: `05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 to before 0b6e59eb885f985a5ea7beed385adfa9412b324d` (git) - affected: `05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 to before 59407ccb52130f2c81f4b3cbe4f14114afceb54f` (git) - Other versions: unaffected - Vendor: Linux. Product: Linux. - affected: `6.3` - unaffected: `before 6.3` (semver) - unaffected: `6.6.157 to 6.6.*, inclusive` (semver) - unaffected: `6.12.110 to 6.12.*, inclusive` (semver) - unaffected: `6.18.52 to 6.18.*, inclusive` (semver) - unaffected: `7.2.6 to 7.2.*, inclusive` (semver) - unaffected: `7.3 to *, inclusive` (original_commit_for_fix) - Other versions: affected ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Linux kernel's arm_scmi firmware driver is affected in several version ranges, with fixes listed for the stable branches 6.6, 6.12, 6.18 and 7.2 and for mainline commits. An attacker who can supply a malformed 32-bit reg value in a device tree node could cause an out-of-range SCMI protocol ID to be truncated or treated as a different protocol. The source gives few details on the resulting impact. Upgrade to a fixed kernel version for your branch, such as 6.6.157, 6.12.110, 6.18.52 or 7.2.6, or later. Written 12 Nov 2026. ## Not analysed yet We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** 0.0022, the 11th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline This record came from the full history of the CVE Program, published 17 Sept 2026. New records show when each source confirmed them. ## Sources - [CVE List: CVE-2026-93085](https://www.cve.org/CVERecord?id=CVE-2026-93085) - [NVD: CVE-2026-93085](https://nvd.nist.gov/vuln/detail/CVE-2026-93085) ### References from the CNA - - - - - - Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description. ## Check whether this affects you This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run. - With the agentprime MCP server (), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: - As JSON: - Everything that needs attention now: --- The web page: . Everything for agents: .