Heimdall Security Logo

CVE-2023-52486

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 6.6.15, 0, <cb4daf271302d71a6b9a7c01bd0b6d76febd8f0c, 6.8, 6.7.3, <bfd0feb1b109cb63b87fdcd00122603787c75a1a, <=5.10.*, <=6.6.*, <9dd334a8245011ace45e53298175c7b659edb3e7, 4.12, 5.15.149, 29dc0d1de18239cf3ef8bab578b8321ed340d81c, <=5.4.*, <=4.19.*, <d7afdf360f4ac142832b098b4de974e867cc063c, 4.19.307, 5.4.269, 5.10.210, <b4af63da9d94986c529d74499fdfe44289acd551, <=*, 6.1.76, <=5.15.*, <376e21a9e4c2c63ee5d8d3aa74be5082c3882229, <f55261469be87c55df13db76dc945f6bcd825105, <4.12, <=6.7.*, <62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0

Description

In the Linux kernel, the following vulnerability has been resolved: drm: Don't unref the same fb many times by mistake due to deadlock handling If we get a deadlock after the fb lookup in drm_mode_page_flip_ioctl() we proceed to unref the fb and then retry the whole thing from the top. But we forget to reset the fb pointer back to NULL, and so if we then get another error during the retry, before the fb lookup, we proceed the unref the same fb again without having gotten another reference. The end result is that the fb will (eventually) end up being freed while it's still in use. Reset fb to NULL once we've unreffed it to avoid doing it again until we've done another fb lookup. This turned out to be pretty easy to hit on a DG2 when doing async flips (and CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y). The first symptom I saw that drm_closefb() simply got stuck in a busy loop while walking the framebuffer list. Fortunately I was able to convince it to oops instead, and from there it was easier to track down the culprit.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 6.6.15, 0, <cb4daf271302d71a6b9a7c01bd0b6d76febd8f0c, 6.8, 6.7.3, <bfd0feb1b109cb63b87fdcd00122603787c75a1a, <=5.10.*, <=6.6.*, <9dd334a8245011ace45e53298175c7b659edb3e7, 4.12, 5.15.149, 29dc0d1de18239cf3ef8bab578b8321ed340d81c, <=5.4.*, <=4.19.*, <d7afdf360f4ac142832b098b4de974e867cc063c, 4.19.307, 5.4.269, 5.10.210, <b4af63da9d94986c529d74499fdfe44289acd551, <=*, 6.1.76, <=5.15.*, <376e21a9e4c2c63ee5d8d3aa74be5082c3882229, <f55261469be87c55df13db76dc945f6bcd825105, <4.12, <=6.7.*, <62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0) 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