CVE-2026-93085

firmware: arm_scmi: Reject out of range DT protocol IDs

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff15a2801d8b90c1b5159618d4bd3a3c65d60f3ff16.3
Vendor states this is fixed in 0b6e59eb885f985a5ea7beed385adfa9412b324d (fixed)
Vendor states this is fixed in 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 (fixed)
Vendor states this is fixed in 59407ccb52130f2c81f4b3cbe4f14114afceb54f (fixed)
Vendor states this is fixed in 8eb2ab209570526728b35e39c4aecdb5099fbaf7 (fixed)
Vendor states this is fixed in e66756313d1b4eadd13f39a0aee9fc8773d4d375 (fixed)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card