VulnerabilityPublished 17 Sep 2026Updated 20 Oct 2026

CVE-2026-93085: Linux kernel · firmware: arm_scmi: Reject out of range DT protocol IDs

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-93085· Medium

Not known to be exploited.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · 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.

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected 6.17.0-5.5 – 7.0.0-38.38 23 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected 6.17.0-1003.3 – 7.0.0-1017.17 15 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected 7.0.0-1003.3 – 7.0.0-1016.16 9 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected 6.17.0-1002.2 – 7.0.0-1014.14 13 affected builds	Fixed in–
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected 7.0.0-1002.3 – 7.0.0-1008.9 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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 apply the updated kernel versions that include this fix. Since this is a kernel-level vulnerability, upgrading to patched kernel versions is the recommended remediation.

Description

A vulnerability in the Linux kernel firmware arm_scmi component allowed out-of-range Device Tree (DT) protocol IDs to be processed incorrectly. The kernel did not properly reject invalid SCMI protocol IDs in message headers, leading to potential misinterpretation of protocol IDs due to truncation or aliasing. This issue has been resolved by skipping DT protocol nodes with invalid protocol IDs during channel setup and device creation.

Impact

The vulnerability could lead to incorrect handling of SCMI protocol IDs, potentially causing misconfiguration or unexpected behavior in protocol device setup within the Linux kernel. There is no indication of active exploitation in the wild or direct compromise impact detailed in the provided data.

Summary

The Linux kernel's arm_scmi firmware component previously accepted SCMI protocol IDs in message headers that exceeded the allowed range defined by MSG_PROTOCOL_ID_MASK. Although the kernel logged errors for these out-of-range IDs, it continued processing them, which could cause malformed 32-bit DT reg values to be truncated or misinterpreted as different protocol IDs. This flaw allowed two distinct out-of-range values to alias the same SCMI protocol identity during channel setup. The fix involves rejecting DT protocol nodes whose reg values do not fit within the SCMI protocol ID field before proceeding with channel or protocol device setup.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 23:29 UTC

Technical details

References

Community reviews

Related threats