CVE-2024-26654

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : 6.9, <=6.1.*, <3c907bf56905de7d27b329afaf59c2fb35d17b04, 198de43d758ca2700e2b52b49c0b189b4931466c, <eeb2a2ca0b8de7e1c66afaf719529154e7dc60b2, 0, 5.15.154, 6.8.3, 2.6.23, <4206ad65a0ee76920041a755bd3c17c6ba59bba2, <=5.10.*, <=6.6.*, 5.10.215, <8c990221681688da34295d6d76cc2f5b963e83f5, <e955e8a7f38a856fc6534ba4e6bffd4d5cc80ac3, <9d66ae0e7bb78b54e1e0525456c6b54e1d132046, <2.6.23, <=5.4.*, 4.19.312, <=4.19.*, <61d4787692c1fccdc268ffa7a891f9c149f50901, <aa39e6878f61f50892ee2dd9d2176f72020be845, 5.4.274, <=6.8.*, 6.7.12, <=*, <=5.15.*, <=6.7.*, <051e0840ffa8ab25554d6b14b62c9ab9e4901457, 6.1.84, 6.6.24

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs The dreamcastcard->timer could schedule the spu_dma_work and the spu_dma_work could also arm the dreamcastcard->timer. When the snd_pcm_substream is closing, the aica_channel will be deallocated. But it could still be dereferenced in the worker thread. The reason is that del_timer() will return directly regardless of whether the timer handler is running or not and the worker could be rescheduled in the timer handler. As a result, the UAF bug will happen. The racy situation is shown below: (Thread 1) | (Thread 2) snd_aicapcm_pcm_close() | ... | run_spu_dma() //worker | mod_timer() flush_work() | del_timer() | aica_period_elapsed() //timer kfree(dreamcastcard->channel) | schedule_work() | run_spu_dma() //worker ... | dreamcastcard->channel-> //USE In order to mitigate this bug and other possible corner cases, call mod_timer() conditionally in run_spu_dma(), then implement PCM sync_stop op to cancel both the timer and worker. The sync_stop op will be called from PCM core appropriately when needed.

Gravité et risque d'exploitation

CVE-2024-26654 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.26 %, ce qui la place devant 16.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.9, <=6.1.*, <3c907bf56905de7d27b329afaf59c2fb35d17b04, 198de43d758ca2700e2b52b49c0b189b4931466c, <eeb2a2ca0b8de7e1c66afaf719529154e7dc60b2, 0, 5.15.154, 6.8.3, 2.6.23, <4206ad65a0ee76920041a755bd3c17c6ba59bba2, <=5.10.*, <=6.6.*, 5.10.215, <8c990221681688da34295d6d76cc2f5b963e83f5, <e955e8a7f38a856fc6534ba4e6bffd4d5cc80ac3, <9d66ae0e7bb78b54e1e0525456c6b54e1d132046, <2.6.23, <=5.4.*, 4.19.312, <=4.19.*, <61d4787692c1fccdc268ffa7a891f9c149f50901, <aa39e6878f61f50892ee2dd9d2176f72020be845, 5.4.274, <=6.8.*, 6.7.12, <=*, <=5.15.*, <=6.7.*, <051e0840ffa8ab25554d6b14b62c9ab9e4901457, 6.1.84, 6.6.24) 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