Heimdall Security Logo

CVE-2023-52608

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <614cc65032dcb0b64d23f5c5e338a8a04b12be5d, <=6.1.*, 6.6.15, <7f95f6997f4fdd17abec3200cae45420a5489350, 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac, 0, 6.8, 6.7.3, <12dc4217f16551d6dee9cbefc23fdb5659558cda, <5.7, <=6.6.*, <9b5e1b93c83ee5fc9f5d7bd2d45b421bd87774a2, 5.15.149, <437a310b22244d4e0b78665c3042e5d1c0f45306, 5.7, <=*, 6.1.76, <=5.15.*, <=6.7.*

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.

Gravité et risque d'exploitation

CVE-2023-52608 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 6.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <614cc65032dcb0b64d23f5c5e338a8a04b12be5d, <=6.1.*, 6.6.15, <7f95f6997f4fdd17abec3200cae45420a5489350, 5c8a47a5a91d4d6e185f758d61997613d9c5d6ac, 0, 6.8, 6.7.3, <12dc4217f16551d6dee9cbefc23fdb5659558cda, <5.7, <=6.6.*, <9b5e1b93c83ee5fc9f5d7bd2d45b421bd87774a2, 5.15.149, <437a310b22244d4e0b78665c3042e5d1c0f45306, 5.7, <=*, 6.1.76, <=5.15.*, <=6.7.*) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE