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-2023-52608firmware: arm_scmi: Check mailbox/SMT channel for consistency

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Check mailbox/SMT channel for consistency On reception of a completion interrupt the shared memory area is accessed to retrieve the message header at first and then, if the message sequence number identifies a transaction which is still pending, the related payload is fetched too. When an SCMI command times out the channel ownership remains with the platform until eventually a late reply is received and, as a consequence, any further transmission attempt remains pending, waiting for the channel to be relinquished by the platform. Once that late reply is received the channel ownership is given back to the agent and any pending request is then allowed to proceed and overwrite the SMT area of the just delivered late reply; then the wait for the reply to the new request starts. It has been observed that the spurious IRQ related to the late reply can be wrongly associated with the freshly enqueued request: when that happens the SCMI stack in-flight lookup procedure is fooled by the fact that the message header now present in the SMT area is related to the new pending transaction, even though the real reply has still to arrive. This race-condition on the A2P channel can be detected by looking at the channel status bits: a genuine reply from the platform will have set the channel free bit before triggering the completion IRQ. Add a consistency check to validate such condition in the A2P ISR.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years 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

CVSS scores of CVE-2023-52608, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 614cc65032dcb0b64d23f5c5e338a8a04b12be5d
    • affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 7f95f6997f4fdd17abec3200cae45420a5489350
    • affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 9b5e1b93c83ee5fc9f5d7bd2d45b421bd87774a2
    • affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 12dc4217f16551d6dee9cbefc23fdb5659558cda
    • affected 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac – < 437a310b22244d4e0b78665c3042e5d1c0f45306

  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.76 – ≤ 6.1.*
    • unaffected 6.6.15 – ≤ 6.6.*
    • unaffected 6.7.3 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .