CVE-2024-26974

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.9, <=6.1.*, 6.6.24, 0, <daba62d9eeddcc5b1081be7d348ca836c83c59d7, <0c2cf5142bfb634c0ef0a1a69cdf37950747d0be, <8e81cd58aee14a470891733181a47d123193ba81, 5.15.154, 6.8.3, <=5.10.*, <=6.6.*, 5.10.215, <8a5a7611ccc7b1fba8d933a9f22a2e76859d94dc, <=5.4.*, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, <d03092550f526a79cf1ade7f0dfa74906f39eb71, <7d42e097607c4d246d99225bf2b195b6167a210c, <226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7, 6.7.12, <=*, <=5.15.*, <=6.7.*, <4ae5a97781ce7d6ecc9c7055396535815b64ca4f, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, <3.17, 3.17, 6.1.84, <bb279ead42263e9fb09480f02a4247b2c287d828

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - resolve race condition during AER recovery During the PCI AER system's error recovery process, the kernel driver may encounter a race condition with freeing the reset_data structure's memory. If the device restart will take more than 10 seconds the function scheduling that restart will exit due to a timeout, and the reset_data structure will be freed. However, this data structure is used for completion notification after the restart is completed, which leads to a UAF bug. This results in a KFENCE bug notice. BUG: KFENCE: use-after-free read in adf_device_reset_worker+0x38/0xa0 [intel_qat] Use-after-free read at 0x00000000bc56fddf (in kfence-#142): adf_device_reset_worker+0x38/0xa0 [intel_qat] process_one_work+0x173/0x340 To resolve this race condition, the memory associated to the container of the work_struct is freed on the worker if the timeout expired, otherwise on the function that schedules the worker. The timeout detection can be done by checking if the caller is still waiting for completion or not by using completion_done() function.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.9, <=6.1.*, 6.6.24, 0, <daba62d9eeddcc5b1081be7d348ca836c83c59d7, <0c2cf5142bfb634c0ef0a1a69cdf37950747d0be, <8e81cd58aee14a470891733181a47d123193ba81, 5.15.154, 6.8.3, <=5.10.*, <=6.6.*, 5.10.215, <8a5a7611ccc7b1fba8d933a9f22a2e76859d94dc, <=5.4.*, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, <d03092550f526a79cf1ade7f0dfa74906f39eb71, <7d42e097607c4d246d99225bf2b195b6167a210c, <226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7, 6.7.12, <=*, <=5.15.*, <=6.7.*, <4ae5a97781ce7d6ecc9c7055396535815b64ca4f, d8cba25d2c68992a6e7c1d329b690a9ebe01167d, <3.17, 3.17, 6.1.84, <bb279ead42263e9fb09480f02a4247b2c287d828) 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