Heimdall Security Logo

CVE-2022-49209

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.3%
Linux•Linux•Versions : 5.15.33, <=5.17.*, <d0b85dfc6f01d26808e2576c6537c131b590e270, 5.18, 4.20, 0, <4.20, <=5.10.*, <de3a8d8fab0710186f7864ec812836d8d70da3c9, 604326b41a6fb9b4a78b6179335decee0365cd8c, <6d03722c34d9603df325f67c6d30dc1b7b3c6067, 5.4.189, <=5.4.*, <9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8, 5.16.19, <=5.16.*, 5.10.110, <bec34a91eba3483e1830c02bdd36f8f968642047, 5.17.2, <f677328f05f52d535cbdc15cb04476db49477eb4, <=*, <=5.15.*

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full If tcp_bpf_sendmsg() is running while sk msg is full. When sk_msg_alloc() returns -ENOMEM error, tcp_bpf_sendmsg() goes to wait_for_memory. If partial memory has been alloced by sk_msg_alloc(), that is, msg_tx->sg.size is greater than osize after sk_msg_alloc(), memleak occurs. To fix we use sk_msg_trim() to release the allocated memory, then goto wait for memory. Other call paths of sk_msg_alloc() have the similar issue, such as tls_sw_sendmsg(), so handle sk_msg_trim logic inside sk_msg_alloc(), as Cong Wang suggested. This issue can cause the following info: WARNING: CPU: 3 PID: 7950 at net/core/stream.c:208 sk_stream_kill_queues+0xd4/0x1a0 Call Trace: <TASK> inet_csk_destroy_sock+0x55/0x110 __tcp_close+0x279/0x470 tcp_close+0x1f/0x60 inet_release+0x3f/0x80 __sock_release+0x3d/0xb0 sock_close+0x11/0x20 __fput+0x92/0x250 task_work_run+0x6a/0xa0 do_exit+0x33b/0xb60 do_group_exit+0x2f/0xa0 get_signal+0xb6/0x950 arch_do_signal_or_restart+0xac/0x2a0 exit_to_user_mode_prepare+0xa9/0x200 syscall_exit_to_user_mode+0x12/0x30 do_syscall_64+0x46/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> WARNING: CPU: 3 PID: 2094 at net/ipv4/af_inet.c:155 inet_sock_destruct+0x13c/0x260 Call Trace: <TASK> __sk_destruct+0x24/0x1f0 sk_psock_destroy+0x19b/0x1c0 process_one_work+0x1b3/0x3c0 kthread+0xe6/0x110 ret_from_fork+0x22/0x30 </TASK>

Gravité et risque d'exploitation

CVE-2022-49209 obtient un score CVSS de 5.5/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.27 %, ce qui la place devant 17.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 5.15.33, <=5.17.*, <d0b85dfc6f01d26808e2576c6537c131b590e270, 5.18, 4.20, 0, <4.20, <=5.10.*, <de3a8d8fab0710186f7864ec812836d8d70da3c9, 604326b41a6fb9b4a78b6179335decee0365cd8c, <6d03722c34d9603df325f67c6d30dc1b7b3c6067, 5.4.189, <=5.4.*, <9c34e38c4a870eb30b13f42f5b44f42e9d19ccb8, 5.16.19, <=5.16.*, 5.10.110, <bec34a91eba3483e1830c02bdd36f8f968642047, 5.17.2, <f677328f05f52d535cbdc15cb04476db49477eb4, <=*, <=5.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