CVE-2024-42232

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.8%
Linux•Linux•Versions : <=6.1.*, <20cf67dcb7db842f941eff1af6ee5e9dc41796d7, <9525af1f58f67df387768770fcf6d6a8f23aee3d, <33d38c5da17f8db2d80e811b7829d2822c10625e, <1177afeca833174ba83504688eec898c6214f4bf, <69c7b2fe4c9cc1d3b1186d1c5606627ecf0de883, 6.10, 0, <4.6, 0e04dc26cc594d31ee6b1382b452b6bc83b57937, 4.19.318, <=5.10.*, <=6.6.*, <=6.9.*, 5.10.222, 6.6.41, 6.9.10, <=5.4.*, 4.6, <2d33654d40a05afd91ab24c9a73ab512a0670a9a, <=4.19.*, <63e5d035e3a7ab7412a008f202633c5e6a0a28ea, <34b76d1922e41da1fa73d43b764cddd82ac9733c, <=*, <=5.15.*, 6.1.100, 5.4.280, 5.15.163

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: fix race between delayed_work() and ceph_monc_stop() The way the delayed work is handled in ceph_monc_stop() is prone to races with mon_fault() and possibly also finish_hunting(). Both of these can requeue the delayed work which wouldn't be canceled by any of the following code in case that happens after cancel_delayed_work_sync() runs -- __close_session() doesn't mess with the delayed work in order to avoid interfering with the hunting interval logic. This part was missed in commit b5d91704f53e ("libceph: behave in mon_fault() if cur_mon < 0") and use-after-free can still ensue on monc and objects that hang off of it, with monc->auth and monc->monmap being particularly susceptible to quickly being reused. To fix this: - clear monc->cur_mon and monc->hunting as part of closing the session in ceph_monc_stop() - bail from delayed_work() if monc->cur_mon is cleared, similar to how it's done in mon_fault() and finish_hunting() (based on monc->hunting) - call cancel_delayed_work_sync() after the session is closed

Gravité et risque d'exploitation

CVE-2024-42232 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.76 %, ce qui la place devant 54.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <20cf67dcb7db842f941eff1af6ee5e9dc41796d7, <9525af1f58f67df387768770fcf6d6a8f23aee3d, <33d38c5da17f8db2d80e811b7829d2822c10625e, <1177afeca833174ba83504688eec898c6214f4bf, <69c7b2fe4c9cc1d3b1186d1c5606627ecf0de883, 6.10, 0, <4.6, 0e04dc26cc594d31ee6b1382b452b6bc83b57937, 4.19.318, <=5.10.*, <=6.6.*, <=6.9.*, 5.10.222, 6.6.41, 6.9.10, <=5.4.*, 4.6, <2d33654d40a05afd91ab24c9a73ab512a0670a9a, <=4.19.*, <63e5d035e3a7ab7412a008f202633c5e6a0a28ea, <34b76d1922e41da1fa73d43b764cddd82ac9733c, <=*, <=5.15.*, 6.1.100, 5.4.280, 5.15.163) 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