CVE-2026-64206Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.8 HIGH (v3.1, CNA)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before 9901f847a762a5d953871dd95767ce2aed3d684d; 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 builds before 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before 8daaf7f73fe998631a160d1a5a7e1b0b0480eef8; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before 8de7b386ffad480ca59222b688c94a2da8f0d805; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before d5616beb3355b5fca2280d796c1cf7ada4ee6551; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before e96fbac8d3a73b0bc165383c092a30628561d320; from 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 before 2641a9e0a1dd4af2e21995470a21d55dd35e5203; and 2 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 3.15.5 before 3.16; from 3.16.1 before 5.10.261; from 5.11 before 5.15.212; from 5.16 before 6.1.178; from 6.2 before 6.6.145; from 6.7 before 6.12.97; from 6.13 before 6.18.39; from 6.19 before 7.1.4; and 8 more ranges | NVD |
References
- https://git.kernel.org/stable/c/fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faapatch
- https://git.kernel.org/stable/c/9901f847a762a5d953871dd95767ce2aed3d684dpatch
- https://git.kernel.org/stable/c/4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081cpatch
- https://git.kernel.org/stable/c/8daaf7f73fe998631a160d1a5a7e1b0b0480eef8patch
- https://git.kernel.org/stable/c/8de7b386ffad480ca59222b688c94a2da8f0d805patch
- https://git.kernel.org/stable/c/d5616beb3355b5fca2280d796c1cf7ada4ee6551patch
- https://git.kernel.org/stable/c/e96fbac8d3a73b0bc165383c092a30628561d320patch
- https://git.kernel.org/stable/c/2641a9e0a1dd4af2e21995470a21d55dd35e5203patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.