Heimdall Security Logo

CVE-2022-49990

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

CVSS 7.8 · Élevée
EPSS 0.3%
Linux•Linux•Versions : 232b47b3c88af1da737cd7760f247c4ed58168cf, 0, <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9, <4.10, 4.19.257, 5.15.64, 4.9.68, 9e51ee1b76efc7b5e9404010793a39fde0e03cb7, 5.10.140, <=5.10.*, 6.0, <cacd522e6652fbc2dc0cc6ae11c4e30782fef14b, <4.5, b8e212c599082896a180a18a0c9bd529526590be, <=5.4.*, <=4.19.*, 5.4.212, 8d9047f8b967ce6181fd824ae922978e1b055cc0, 5.19.6, <25a95303b9e513cd2978aacc385d06e6fec23d07, <8195e065abf3df84eb0ad2987e76a40f21d1791c, 4.4.105, <297ae7e87a87a001dd3dfeac1cb26a42fd929708, 4.14.5, <=*, <=5.15.*, <=5.19.*, <4.15, <fbdc482d43eda40a70de4b0155843d5472f6de62, 4.15

Description

In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are initially copied on fork() via arch_dup_task_struct() and then cleared via copy_thread() before fork() returns. If fork() happens to fail after the initial task dup and before copy_thread(), the newly allocated task and associated thread_struct memory are freed via free_task() -> arch_release_task_struct(). This results in a double free of the guarded storage and runtime info structs because the fields in the failed task still refer to memory associated with the source task. This problem can manifest as a BUG_ON() in set_freepointer() (with CONFIG_SLAB_FREELIST_HARDENED enabled) or KASAN splat (if enabled) when running trinity syscall fuzz tests on s390x. To avoid this problem, clear the associated pointer fields in arch_dup_task_struct() immediately after the new task is copied. Note that the RI flag is still cleared in copy_thread() because it resides in thread stack memory and that is where stack info is copied.

Gravité et risque d'exploitation

CVE-2022-49990 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 232b47b3c88af1da737cd7760f247c4ed58168cf, 0, <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9, <4.10, 4.19.257, 5.15.64, 4.9.68, 9e51ee1b76efc7b5e9404010793a39fde0e03cb7, 5.10.140, <=5.10.*, 6.0, <cacd522e6652fbc2dc0cc6ae11c4e30782fef14b, <4.5, b8e212c599082896a180a18a0c9bd529526590be, <=5.4.*, <=4.19.*, 5.4.212, 8d9047f8b967ce6181fd824ae922978e1b055cc0, 5.19.6, <25a95303b9e513cd2978aacc385d06e6fec23d07, <8195e065abf3df84eb0ad2987e76a40f21d1791c, 4.4.105, <297ae7e87a87a001dd3dfeac1cb26a42fd929708, 4.14.5, <=*, <=5.15.*, <=5.19.*, <4.15, <fbdc482d43eda40a70de4b0155843d5472f6de62, 4.15) 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