VulnerabilityPublished 17 Sep 2026Updated 30 Oct 2026

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

Source GCVE Database

Compare

Authoritative record:CVE-2026-93085· Medium

Not known to be exploited · fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 18:18 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375, 59407ccb52130f2c81f4b3cbe4f14114afceb54f, 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-6jx6-f56j-v3c4

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1, < e66756313d1b4eadd13f39a0aee9fc8773d4d375	Fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375
LinuxLinux	Affected ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1, < 59407ccb52130f2c81f4b3cbe4f14114afceb54f	Fixed in 59407ccb52130f2c81f4b3cbe4f14114afceb54f
LinuxLinux	Affected ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1, < 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1	Fixed in 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1
LinuxLinux	Affected ≥ 22f7f35fd71b597a5d916e41d7646be6ee530c86, < 75d6273a28cdb543a167ac5fbfca75dc286ffe10	Fixed in 75d6273a28cdb543a167ac5fbfca75dc286ffe10
LinuxLinux	Affected ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1, < 8eb2ab209570526728b35e39c4aecdb5099fbaf7	Fixed in 8eb2ab209570526728b35e39c4aecdb5099fbaf7
LinuxLinux	Affected ≥ 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1, < 0b6e59eb885f985a5ea7beed385adfa9412b324d	Fixed in 0b6e59eb885f985a5ea7beed385adfa9412b324d

AI-suggested

The issue has been resolved in the Linux kernel by adding checks to skip DT protocol nodes with reg values that do not fit the SCMI protocol ID field before setting up channels or creating protocol devices. Users should apply the official kernel updates that include this fix. No additional mitigation steps are indicated.

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 SCMI protocol IDs in message headers exceeding the allowed range defined by MSG_PROTOCOL_ID_MASK. The kernel logged errors for these invalid IDs but continued processing them, which could lead to truncation or misinterpretation of the protocol ID. This flaw affected channel setup and protocol device creation by allowing malformed 32-bit DT reg values to be used improperly. The vulnerability has been resolved by skipping DT protocol nodes with invalid reg values before channel setup or device creation.

References

Community reviews

Loading reviews…