Heimdall Security Logo

CVE-2026-43023

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, 6.6.134, 7.0, <d002bd11024bd231bcb606877e33951ffb7bed14, <6.1.168, <6.3, <=6.6.*, <=6.19.*, 6.1.109, 6.3, 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3, <adb90cd0f9f7a8d438fcb93354040fbafc5ae2a0, <98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8d, <=6.18.*, 70a13b1e25fef37c87c8a1228ddb8900efbca7cf, 6.12.81, <=*, <7e296ffdab5bdab718dff7c14288fdcb9154fa27, 6.1.168, <dabf22269242e2f2bf44c43fcdc2fa763df7f9cc, 6.18.22, <8a5b0135d4a5d9683203a3d9a12a711ccec5936b, 6.19.12

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: fix race conditions in sco_sock_connect() sco_sock_connect() checks sk_state and sk_type without holding the socket lock. Two concurrent connect() syscalls on the same socket can both pass the check and enter sco_connect(), leading to use-after-free. The buggy scenario involves three participants and was confirmed with additional logging instrumentation: Thread A (connect): HCI disconnect: Thread B (connect): sco_sock_connect(sk) sco_sock_connect(sk) sk_state==BT_OPEN sk_state==BT_OPEN (pass, no lock) (pass, no lock) sco_connect(sk): sco_connect(sk): hci_dev_lock hci_dev_lock hci_connect_sco <- blocked -> hcon1 sco_conn_add->conn1 lock_sock(sk) sco_chan_add: conn1->sk = sk sk->conn = conn1 sk_state=BT_CONNECT release_sock hci_dev_unlock hci_dev_lock sco_conn_del: lock_sock(sk) sco_chan_del: sk->conn=NULL conn1->sk=NULL sk_state= BT_CLOSED SOCK_ZAPPED release_sock hci_dev_unlock (unblocked) hci_connect_sco -> hcon2 sco_conn_add -> conn2 lock_sock(sk) sco_chan_add: sk->conn=conn2 sk_state= BT_CONNECT // zombie sk! release_sock hci_dev_unlock Thread B revives a BT_CLOSED + SOCK_ZAPPED socket back to BT_CONNECT. Subsequent cleanup triggers double sock_put() and use-after-free. Meanwhile conn1 is leaked as it was orphaned when sco_conn_del() cleared the association. Fix this by: - Moving lock_sock() before the sk_state/sk_type checks in sco_sock_connect() to serialize concurrent connect attempts - Fixing the sk_type != SOCK_SEQPACKET check to actually return the error instead of just assigning it - Adding a state re-check in sco_connect() after lock_sock() to catch state changes during the window between the locks - Adding sco_pi(sk)->conn check in sco_chan_add() to prevent double-attach of a socket to multiple connections - Adding hci_conn_drop() on sco_chan_add failure to prevent HCI connection leaks

Gravité et risque d'exploitation

CVE-2026-43023 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.10 %, ce qui la place devant 0.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, 6.6.134, 7.0, <d002bd11024bd231bcb606877e33951ffb7bed14, <6.1.168, <6.3, <=6.6.*, <=6.19.*, 6.1.109, 6.3, 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3, <adb90cd0f9f7a8d438fcb93354040fbafc5ae2a0, <98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8d, <=6.18.*, 70a13b1e25fef37c87c8a1228ddb8900efbca7cf, 6.12.81, <=*, <7e296ffdab5bdab718dff7c14288fdcb9154fa27, 6.1.168, <dabf22269242e2f2bf44c43fcdc2fa763df7f9cc, 6.18.22, <8a5b0135d4a5d9683203a3d9a12a711ccec5936b, 6.19.12) 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