Answer in brief
CVE-2026-93085 records a Unknown severity vulnerability in firmware: arm_scmi: Reject out of range DT protocol IDs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <8eb2ab209570526728b35e39c4aecdb5099fbaf7 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <e66756313d1b4eadd13f39a0aee9fc8773d4d375 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <0b6e59eb885f985a5ea7beed385adfa9412b324d || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <59407ccb52130f2c81f4b3cbe4f14114afceb54f | 8eb2ab209570526728b35e39c4aecdb5099fbaf7, 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1, e66756313d1b4eadd13f39a0aee9fc8773d4d375, 0b6e59eb885f985a5ea7beed385adfa9412b324d, 59407ccb52130f2c81f4b3cbe4f14114afceb54f |
| Linux/Linuxgeneric | 6.3 | Not reported |
| Linux/Linuxgeneric | >=22f7f35fd71b597a5d916e41d7646be6ee530c86 <75d6273a28cdb543a167ac5fbfca75dc286ffe10 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <8eb2ab209570526728b35e39c4aecdb5099fbaf7 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <e66756313d1b4eadd13f39a0aee9fc8773d4d375 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <0b6e59eb885f985a5ea7beed385adfa9412b324d || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <59407ccb52130f2c81f4b3cbe4f14114afceb54f | 75d6273a28cdb543a167ac5fbfca75dc286ffe10, 8eb2ab209570526728b35e39c4aecdb5099fbaf7, 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1, e66756313d1b4eadd13f39a0aee9fc8773d4d375, 0b6e59eb885f985a5ea7beed385adfa9412b324d, 59407ccb52130f2c81f4b3cbe4f14114afceb54f |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.