Heimdall Security Logo

CVE-2022-49326

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.3%
Linux•Linux•Versions : <=5.17.*, <3.15, 5.15.46, 0, <b8ce58ab80faaea015c206382041ff3bcf5495ff, 5.19, <=4.9.*, <769ec2a824deae2f1268dfda14999a4d14d0d0c5, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <746285cf81dc19502ab238249d75f5990bd2d231, 3.15, <=5.4.*, 4.14.283, <=4.19.*, <9ad1981fc4de3afb7db3e8eb5a6a52d4c7d0d577, fd6564fcdc0bfcd432e6e939f9538acc3905d08a, <b5dca2cd3f0239512da808598b4e70557eb4c2a1, <=*, <=5.15.*, <98e55b0b876bde3353f4e074883d66ecb55c65a3, <6ad81ad0cf5744738ce94c8e64051ddd80a1734c, 4.9.318, <9d5e96cc1f1720019ce27b127a31695148d38bb0, <d7e30dfc166d33470bba31a42f9bbc346e5409d5

Description

In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum: https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html He also confirmed that this patch fixes the issue. In summary this happened: After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a "divide error: 0000" when connecting to an AP. Control port tx now tries to use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in 2.10. Since only the rtl8187se part of the driver supports QoS, the priority of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185 cards. rtl8180 is then unconditionally reading out the priority and finally crashes on drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this patch: idx = (ring->idx + skb_queue_len(&ring->queue)) % ring->entries "ring->entries" is zero for rtl8180/rtl8185 cards, tx_ring[2] never got initialized.

Gravité et risque d'exploitation

CVE-2022-49326 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.30 %, ce qui la place devant 20.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=5.17.*, <3.15, 5.15.46, 0, <b8ce58ab80faaea015c206382041ff3bcf5495ff, 5.19, <=4.9.*, <769ec2a824deae2f1268dfda14999a4d14d0d0c5, 5.18.3, <=5.10.*, <=4.14.*, 5.10.121, 5.17.14, 4.19.247, 5.4.198, <=5.18.*, <746285cf81dc19502ab238249d75f5990bd2d231, 3.15, <=5.4.*, 4.14.283, <=4.19.*, <9ad1981fc4de3afb7db3e8eb5a6a52d4c7d0d577, fd6564fcdc0bfcd432e6e939f9538acc3905d08a, <b5dca2cd3f0239512da808598b4e70557eb4c2a1, <=*, <=5.15.*, <98e55b0b876bde3353f4e074883d66ecb55c65a3, <6ad81ad0cf5744738ce94c8e64051ddd80a1734c, 4.9.318, <9d5e96cc1f1720019ce27b127a31695148d38bb0, <d7e30dfc166d33470bba31a42f9bbc346e5409d5) 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