CVE-2022-48909

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 5.10.104, <2e8d465b83db307f04ad265848f8ab3f78f6918f, <=*, 5.3, <=5.15.*, 39f41f367b08650e9aa314e3a13fb6dda1e9eec7, <5.3, <=5.10.*, <e98d46ccfa84b35a9e4b1ccdd83961b41a5d7ce5, 5.16.13, 0, 5.15.27, 5.17, <=5.16.*, <9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5, <80895b6f9154fb22d36fab311ccbb75503a2c87b

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix connection leak There's a potential leak issue under following execution sequence : smc_release smc_connect_work if (sk->sk_state == SMC_INIT) send_clc_confirim tcp_abort(); ... sk.sk_state = SMC_ACTIVE smc_close_active switch(sk->sk_state) { ... case SMC_ACTIVE: smc_close_final() // then wait peer closed Unfortunately, tcp_abort() may discard CLC CONFIRM messages that are still in the tcp send buffer, in which case our connection token cannot be delivered to the server side, which means that we cannot get a passive close message at all. Therefore, it is impossible for the to be disconnected at all. This patch tries a very simple way to avoid this issue, once the state has changed to SMC_ACTIVE after tcp_abort(), we can actively abort the smc connection, considering that the state is SMC_INIT before tcp_abort(), abandoning the complete disconnection process should not cause too much problem. In fact, this problem may exist as long as the CLC CONFIRM message is not received by the server. Whether a timer should be added after smc_close_final() needs to be discussed in the future. But even so, this patch provides a faster release for connection in above case, it should also be valuable.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 5.10.104, <2e8d465b83db307f04ad265848f8ab3f78f6918f, <=*, 5.3, <=5.15.*, 39f41f367b08650e9aa314e3a13fb6dda1e9eec7, <5.3, <=5.10.*, <e98d46ccfa84b35a9e4b1ccdd83961b41a5d7ce5, 5.16.13, 0, 5.15.27, 5.17, <=5.16.*, <9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5, <80895b6f9154fb22d36fab311ccbb75503a2c87b) 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