CVE-2026-64206

CVE CVE-2026-64206EUVD EUVD-2026-46014Published 2026-07-20T16:27:53.000ZLast changed 2026-08-05T12:40:00.000ZCVSS 8.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 6.1.178; patch: 7.1.4; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <8de7b386ffad480ca59222b688c94a2da8f0d805; 3.15.5 <3.16; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa; patch: 5.10.261; patch: 6.6.145; ee805f9499ebd0edf0877990968543c752043b59; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c; patch: 5.15.212; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <2641a9e0a1dd4af2e21995470a21d55dd35e5203; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <8daaf7f73fe998631a160d1a5a7e1b0b0480eef8; patch: 0; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <e96fbac8d3a73b0bc165383c092a30628561d320; 3.16; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <d5616beb3355b5fca2280d796c1cf7ada4ee6551; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <9901f847a762a5d953871dd95767ce2aed3d684d; patch: 7.2-rc3; patch: 6.18.39; patch: 6.12.97

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.