Heimdall Security Logo

CVE-2022-49607

Vulnérabilité moyenne dans Linux (Linux)

CVSS 4.7 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : c52217e88ae0f3a4ae00562d86e338f8f85969b4, 5.15.58, <98c3c8fd0d4c560e0f8335b79c407bbf7fc9462c, 3.4.52, 0, 5.18.15, 4.9.325, 5.19, <43128b3eee337824158f34da6648163d2f2fb937, 4.14.290, <3.3, 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b, <3bbd868099287ff9027db59029b502fcfa2202a0, <f836f9ac95df15f1e0af4beb0ec20021e8c91998, <=4.9.*, <3.10, <=5.10.*, <=4.14.*, 703197b61d05f5edae54bad3256901c5a5c8794c, 4.19.254, 3.2.49, <=5.18.*, <a9391ff7a7c5f113d6f2bf6621d49110950de49c, <=5.4.*, <3.5, <=4.19.*, <68e3c69803dada336893640110cb87221bb01dcf, 5.10.134, <17f5417194136517ee9bbd6511249e5310e5617c, <=*, <=5.15.*, 3.10, 5.4.208, <da3c256e2d0ebc87c7db0c605c9692b6f1722074, 3.9.8, 2487f0db30527032c4d56fc2d0b1a240fe89fef8

Description

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() Yang Jihing reported a race between perf_event_set_output() and perf_mmap_close(): CPU1 CPU2 perf_mmap_close(e2) if (atomic_dec_and_test(&e2->rb->mmap_count)) // 1 - > 0 detach_rest = true ioctl(e1, IOC_SET_OUTPUT, e2) perf_event_set_output(e1, e2) ... list_for_each_entry_rcu(e, &e2->rb->event_list, rb_entry) ring_buffer_attach(e, NULL); // e1 isn't yet added and // therefore not detached ring_buffer_attach(e1, e2->rb) list_add_rcu(&e1->rb_entry, &e2->rb->event_list) After this; e1 is attached to an unmapped rb and a subsequent perf_mmap() will loop forever more: again: mutex_lock(&e->mmap_mutex); if (event->rb) { ... if (!atomic_inc_not_zero(&e->rb->mmap_count)) { ... mutex_unlock(&e->mmap_mutex); goto again; } } The loop in perf_mmap_close() holds e2->mmap_mutex, while the attach in perf_event_set_output() holds e1->mmap_mutex. As such there is no serialization to avoid this race. Change perf_event_set_output() to take both e1->mmap_mutex and e2->mmap_mutex to alleviate that problem. Additionally, have the loop in perf_mmap() detach the rb directly, this avoids having to wait for the concurrent perf_mmap_close() to get around to doing it to make progress.

Gravité et risque d'exploitation

CVE-2022-49607 obtient un score CVSS de 4.7/10, soit une gravité moyenne. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.19 %, ce qui la place devant 7.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions c52217e88ae0f3a4ae00562d86e338f8f85969b4, 5.15.58, <98c3c8fd0d4c560e0f8335b79c407bbf7fc9462c, 3.4.52, 0, 5.18.15, 4.9.325, 5.19, <43128b3eee337824158f34da6648163d2f2fb937, 4.14.290, <3.3, 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b, <3bbd868099287ff9027db59029b502fcfa2202a0, <f836f9ac95df15f1e0af4beb0ec20021e8c91998, <=4.9.*, <3.10, <=5.10.*, <=4.14.*, 703197b61d05f5edae54bad3256901c5a5c8794c, 4.19.254, 3.2.49, <=5.18.*, <a9391ff7a7c5f113d6f2bf6621d49110950de49c, <=5.4.*, <3.5, <=4.19.*, <68e3c69803dada336893640110cb87221bb01dcf, 5.10.134, <17f5417194136517ee9bbd6511249e5310e5617c, <=*, <=5.15.*, 3.10, 5.4.208, <da3c256e2d0ebc87c7db0c605c9692b6f1722074, 3.9.8, 2487f0db30527032c4d56fc2d0b1a240fe89fef8) 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