CVE-2024-41012

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <2.6.13, c293621bbf678a3d85e3ed721c3921c8a670610d, 6.10, <52c87ab18c76c14d7209646ccb3283b3f5d87b22, 0, 6.1.101, <5f5d0799eb0a01d550c21b7894e26b2d9db55763, 2.6.13, 6.6.42, <=5.10.*, 5.15.164, <=6.6.*, <=6.9.*, <5661b9c7ec189406c2dde00837aaa4672efb6240, 5.10.223, <dc2ce1dfceaa0767211a9d963ddb029ab21c4235, <=5.4.*, 6.9.9, <=4.19.*, <d30ff33040834c3b9eee29740acd92f9c7ba2250, <3cad1bc010416c6dd780643476bc59ed742436b9, <b6d223942c34057fdfd8f149e763fa823731b224, 4.19.319, <=*, <=5.15.*, 5.4.281, <ef8fc41cd6f95f9a4a3470f085aecf350569a0b3

Description

In the Linux kernel, the following vulnerability has been resolved: filelock: Remove locks reliably when fcntl/close race is detected When fcntl_setlk() races with close(), it removes the created lock with do_lock_file_wait(). However, LSMs can allow the first do_lock_file_wait() that created the lock while denying the second do_lock_file_wait() that tries to remove the lock. Separately, posix_lock_file() could also fail to remove a lock due to GFP_KERNEL allocation failure (when splitting a range in the middle). After the bug has been triggered, use-after-free reads will occur in lock_get_status() when userspace reads /proc/locks. This can likely be used to read arbitrary kernel memory, but can't corrupt kernel memory. Fix it by calling locks_remove_posix() instead, which is designed to reliably get rid of POSIX locks associated with the given file and files_struct and is also used by filp_flush().

Gravité et risque d'exploitation

CVE-2024-41012 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.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2.6.13, c293621bbf678a3d85e3ed721c3921c8a670610d, 6.10, <52c87ab18c76c14d7209646ccb3283b3f5d87b22, 0, 6.1.101, <5f5d0799eb0a01d550c21b7894e26b2d9db55763, 2.6.13, 6.6.42, <=5.10.*, 5.15.164, <=6.6.*, <=6.9.*, <5661b9c7ec189406c2dde00837aaa4672efb6240, 5.10.223, <dc2ce1dfceaa0767211a9d963ddb029ab21c4235, <=5.4.*, 6.9.9, <=4.19.*, <d30ff33040834c3b9eee29740acd92f9c7ba2250, <3cad1bc010416c6dd780643476bc59ed742436b9, <b6d223942c34057fdfd8f149e763fa823731b224, 4.19.319, <=*, <=5.15.*, 5.4.281, <ef8fc41cd6f95f9a4a3470f085aecf350569a0b3) 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