Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93085

firmware: arm_scmi: Reject out of range DT protocol IDs

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 22f7f35fd71b597a5d916e41d7646be6ee530c86 – < 75d6273a28cdb543a167ac5fbfca75dc286ffe10
    • affected 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 – < 8eb2ab209570526728b35e39c4aecdb5099fbaf7
    • affected 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 – < 5142fd31bd8c9aff9bad4f6e0cc20e9574f2cee1
    • affected 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 – < e66756313d1b4eadd13f39a0aee9fc8773d4d375
    • affected 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 – < 0b6e59eb885f985a5ea7beed385adfa9412b324d
    • affected 05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 – < 59407ccb52130f2c81f4b3cbe4f14114afceb54f
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93085 badge
[![CVE-2026-93085](https://cveledger.app/badge/CVE-2026-93085.svg)](https://cveledger.app/cve/CVE-2026-93085)

Record last updated .