SECUFOCUSNOW
Home›CVE index›CVE-2026-64206
Review reviewHigh

CVE-2026-64206

Linux

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) tea...

CVSS
8.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 8.8

Vulnerability overview

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) tea...

Affected product and versions

Product
Linux
Affected versions
>= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < 9901f847a762a5d953871dd95767ce2aed3d684d, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < 8daaf7f73fe998631a160d1a5a7e1b0b0480eef8, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < 8de7b386ffad480ca59222b688c94a2da8f0d805, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < d5616beb3355b5fca2280d796c1cf7ada4ee6551, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < e96fbac8d3a73b0bc165383c092a30628561d320, >= 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 < 2641a9e0a1dd4af2e21995470a21d55dd35e5203, >= ee805f9499ebd0edf0877990968543c752043b59, >= 3.15.5 < 3.16, >= 3.16
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available