CVE-2026-64206

Service interruption via L2CAP teardown deadlock

Published Jul 20, 2026 · Updated Jul 20, 2026

Race condition in the Linux Kernel Bluetooth L2CAP subsystem allows physically proximate attackers to deadlock connection teardown. The l2cap_conn_del() path holds conn->lock while cancel_work_sync() waits for pending_rx_work, whose process_pending_rx() worker needs the same mutex, creating a circular wait. Bluetooth L2CAP must be present and processing a connection teardown; the published evidence demonstrates a deadlock, not memory corruption or code execution.

CVSS severity8.8
High
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in the Linux Kernel Bluetooth L2CAP subsystem allows physically proximate attackers to deadlock connection teardown. The l2cap_conn_del() path holds conn->lock while cancel_work_sync() waits for pending_rx_work, whose process_pending_rx() worker needs the same mutex, creating a circular wait. Bluetooth L2CAP must be present and processing a connection teardown; the published evidence demonstrates a deadlock, not memory corruption or code execution.

The record

CVE
CVE-2026-64206
Published
Jul 20, 2026
Updated
Jul 20, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
T1499
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.15.5 <3.16
  2. Affected versionversion=3.16
  3. Affected versionversion=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <2641a9e0a1dd4af2e21995470a21d55dd35e5203
  4. Affected versionversion=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <d5616beb3355b5fca2280d796c1cf7ada4ee6551
  5. Affected versionversion=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <e96fbac8d3a73b0bc165383c092a30628561d320
  6. Affected versionversion=ee805f9499ebd0edf0877990968543c752043b59

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=3.15.5 <3.16; version=3.16; version=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <2641a9e0a1dd4af2e21995470a21d55dd35e5203; version=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <d5616beb3355b5fca2280d796c1cf7ada4ee6551; version=7ab56c3a6eccb215034b0cb096e0313441cbf2a4 <e96fbac8d3a73b0bc165383c092a30628561d320; version=ee805f9499ebd0edf0877990968543c752043b59

Published CVSS scores

8.8kernel.orgCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo