Heimdall Security Logo

CVE-2022-48926

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 5.15.26, <aaaba1c86d04dac8e49bf508b492f81506257da3, 5.4.182, <9f688aadede6b862a0a898792b1a35421c93636f, 0, <4.6, 5.16.12, <=4.9.*, <=5.10.*, <=4.14.*, <4ce247af3f30078d5b97554f1ae6200a0222c15a, <=5.4.*, 4.6, <9f5d8ba538ef81cd86ea587ca3f8c77e26bea405, 4.19.232, 4.14.269, <=4.19.*, 4.9.304, <=5.16.*, <9ab652d41deab49848673c3dadb57ad338485376, 5.10.103, <da514063440b53a27309a4528b726f92c3cfe56f, <=*, <=5.15.*, <33222d1571d7ce8c1c75f6b488f38968fa93d2d9, f6281af9d62e128aa6efad29cf7265062af114f2, <669c2b178956718407af5631ccbc61c24413f038, 5.17

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: rndis: add spinlock for rndis response list There's no lock for rndis response list. It could cause list corruption if there're two different list_add at the same time like below. It's better to add in rndis_add_response / rndis_free_response / rndis_get_next_response to prevent any race condition on response list. [ 361.894299] [1: irq/191-dwc3:16979] list_add corruption. next->prev should be prev (ffffff80651764d0), but was ffffff883dc36f80. (next=ffffff80651764d0). [ 361.904380] [1: irq/191-dwc3:16979] Call trace: [ 361.904391] [1: irq/191-dwc3:16979] __list_add_valid+0x74/0x90 [ 361.904401] [1: irq/191-dwc3:16979] rndis_msg_parser+0x168/0x8c0 [ 361.904409] [1: irq/191-dwc3:16979] rndis_command_complete+0x24/0x84 [ 361.904417] [1: irq/191-dwc3:16979] usb_gadget_giveback_request+0x20/0xe4 [ 361.904426] [1: irq/191-dwc3:16979] dwc3_gadget_giveback+0x44/0x60 [ 361.904434] [1: irq/191-dwc3:16979] dwc3_ep0_complete_data+0x1e8/0x3a0 [ 361.904442] [1: irq/191-dwc3:16979] dwc3_ep0_interrupt+0x29c/0x3dc [ 361.904450] [1: irq/191-dwc3:16979] dwc3_process_event_entry+0x78/0x6cc [ 361.904457] [1: irq/191-dwc3:16979] dwc3_process_event_buf+0xa0/0x1ec [ 361.904465] [1: irq/191-dwc3:16979] dwc3_thread_interrupt+0x34/0x5c

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 5.15.26, <aaaba1c86d04dac8e49bf508b492f81506257da3, 5.4.182, <9f688aadede6b862a0a898792b1a35421c93636f, 0, <4.6, 5.16.12, <=4.9.*, <=5.10.*, <=4.14.*, <4ce247af3f30078d5b97554f1ae6200a0222c15a, <=5.4.*, 4.6, <9f5d8ba538ef81cd86ea587ca3f8c77e26bea405, 4.19.232, 4.14.269, <=4.19.*, 4.9.304, <=5.16.*, <9ab652d41deab49848673c3dadb57ad338485376, 5.10.103, <da514063440b53a27309a4528b726f92c3cfe56f, <=*, <=5.15.*, <33222d1571d7ce8c1c75f6b488f38968fa93d2d9, f6281af9d62e128aa6efad29cf7265062af114f2, <669c2b178956718407af5631ccbc61c24413f038, 5.17) 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