# CVE-2026-93085: firmware: arm_scmi: Reject out of range DT protocol IDs

> A flaw in the Linux kernel SCMI driver allows out-of-range protocol IDs to cause truncation and aliasing, potentially leading to privilege escalation or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101957, BELL-CVE-2026-93085, DEBIAN-CVE-2026-93085, GHSA-6jx6-f56j-v3c4, UBUNTU-CVE-2026-93085

## What is CVE-2026-93085?

CVE-2026-93085 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93085?


## How do I fix CVE-2026-93085?

Apply the vendor's patch.

## Is CVE-2026-93085 being exploited?

There is no known exploitation of CVE-2026-93085 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93085 and fix it if it is affected.

What it is: CVE-2026-93085 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93085 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93085/ (Markdown: https://insights.sbomify.com/CVE-2026-93085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93085
- OSV: https://osv.dev/vulnerability/CVE-2026-93085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93085/
Summaries are generated and may contain mistakes; the official description above is the record.