CVE-2023-52625

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.8, <=*, 6.7.3, <=6.7.*, <820c3870c491946a78950cdf961bf40e28c1025f, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 0, <4.15, 4.15, <8e57c06bf4b0f51a4d6958e15e1a99c9520d00fa

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Refactor DMCUB enter/exit idle interface [Why] We can hang in place trying to send commands when the DMCUB isn't powered on. [How] We need to exit out of the idle state prior to sending a command, but the process that performs the exit also invokes a command itself. Fixing this issue involves the following: 1. Using a software state to track whether or not we need to start the process to exit idle or notify idle. It's possible for the hardware to have exited an idle state without driver knowledge, but entering one is always restricted to a driver allow - which makes the SW state vs HW state mismatch issue purely one of optimization, which should seldomly be hit, if at all. 2. Refactor any instances of exit/notify idle to use a single wrapper that maintains this SW state. This works simialr to dc_allow_idle_optimizations, but works at the DMCUB level and makes sure the state is marked prior to any notify/exit idle so we don't enter an infinite loop. 3. Make sure we exit out of idle prior to sending any commands or waiting for DMCUB idle. This patch takes care of 1/2. A future patch will take care of wrapping DMCUB command submission with calls to this new interface.

Gravité et risque d'exploitation

CVE-2023-52625 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.20 %, ce qui la place devant 9.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.8, <=*, 6.7.3, <=6.7.*, <820c3870c491946a78950cdf961bf40e28c1025f, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 0, <4.15, 4.15, <8e57c06bf4b0f51a4d6958e15e1a99c9520d00fa) 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