CVE-2026-64206

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock l2cap_conn_del() takes conn->lock and then calls cancel_work_sync() for pending_rx_work. process_pending_rx() takes the same mutex, so teardown can deadlock against the worker it is flushing. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the l2cap_conn_ready() -> queue_work(..., &conn->pending_rx_work) submit path, the l2cap_conn_del() -> cancel_work_sync(&conn->pending_rx_work) teardown path, and the process_pending_rx() -> mutex_lock(&conn->lock) worker edge. Lockdep WARNING: possible circular locking dependency detected process_pending_rx+0x21/0x2a [vuln_msv] l2cap_conn_del.constprop.0+0x3f/0x4e [vuln_msv] *** DEADLOCK *** Cancel pending_rx_work before taking conn->lock, matching the existing lock-before-drain ordering used for the two delayed works in the same teardown path. The pending_rx queue is still purged after the work has been cancelled and conn->lock has been acquired.

Gravité et risque d'exploitation

CVE-2026-64206 obtient un score CVSS de 8.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.26 %, ce qui la place devant 16.5 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <d5616beb3355b5fca2280d796c1cf7ada4ee6551, <=6.1.*, <e96fbac8d3a73b0bc165383c092a30628561d320, <=6.12.*, ee805f9499ebd0edf0877990968543c752043b59, 6.18.39, <8daaf7f73fe998631a160d1a5a7e1b0b0480eef8, <2641a9e0a1dd4af2e21995470a21d55dd35e5203, 0, 7ab56c3a6eccb215034b0cb096e0313441cbf2a4, 3.15.5, <=7.1.*, 7.1.4, <9901f847a762a5d953871dd95767ce2aed3d684d, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <=*, <=5.15.*, <3.16, 3.16, <fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa, <8de7b386ffad480ca59222b688c94a2da8f0d805, 7.2) 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

• https://git.kernel.org/stable/c/fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa
• https://git.kernel.org/stable/c/9901f847a762a5d953871dd95767ce2aed3d684d
• https://git.kernel.org/stable/c/4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c
• https://git.kernel.org/stable/c/8daaf7f73fe998631a160d1a5a7e1b0b0480eef8
• https://git.kernel.org/stable/c/8de7b386ffad480ca59222b688c94a2da8f0d805
• https://git.kernel.org/stable/c/d5616beb3355b5fca2280d796c1cf7ada4ee6551
• https://git.kernel.org/stable/c/e96fbac8d3a73b0bc165383c092a30628561d320
• https://git.kernel.org/stable/c/2641a9e0a1dd4af2e21995470a21d55dd35e5203