CVE-2026-64206: Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2641a9e0a1dd4af2e21995470a21d55dd35e5203, 3.16, 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2641a9e0a1dd4af2e21995470a21d55dd35e5203, 3.16, 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 20, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-362
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.15.5 and later · before 3.16
- linux linux kernel3.16.1 and later · before 5.10.261
- linux linux kernel5.11 and later · before 5.15.212
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.97
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
- linux linux kernel3.16
- linux linux kernel7.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- ee805f9499ebd0edf0877990968543c752043b59, 3.16affected
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faaaffected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before 9901f847a762a5d953871dd95767ce2aed3d684daffected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081caffected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before 8daaf7f73fe998631a160d1a5a7e1b0b0480eef8affected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before 8de7b386ffad480ca59222b688c94a2da8f0d805affected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before d5616beb3355b5fca2280d796c1cf7ada4ee6551affected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before e96fbac8d3a73b0bc165383c092a30628561d320affected · git
- 7ab56c3a6eccb215034b0cb096e0313441cbf2a4 and later · before 2641a9e0a1dd4af2e21995470a21d55dd35e5203affected · git
- 3.15.5 and later · before 3.16affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.1.7-1.1 | 7.1.7-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64192Jul 20, 2026 · bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized22Monitor
- ← EarlierCVE-2026-64205Jul 20, 2026 · i2c: i801: fix hardware state machine corruption in error path22Monitor
- Later →CVE-2026-64600Jul 23, 2026 · xfs: resample the data fork mapping after cycling ILOCK31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2641a9e0a1dd4af2e21995470a21d55dd35e5203 | Vendor (CNA) |
| Linux Linux | 3.16 | Vendor (CNA) |
| Linux Linux | 4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c | Vendor (CNA) |
| Linux Linux | 8daaf7f73fe998631a160d1a5a7e1b0b0480eef8 | Vendor (CNA) |
| Linux Linux | 8de7b386ffad480ca59222b688c94a2da8f0d805 | Vendor (CNA) |
| Linux Linux | 9901f847a762a5d953871dd95767ce2aed3d684d | Vendor (CNA) |
| Linux Linux | d5616beb3355b5fca2280d796c1cf7ada4ee6551 | Vendor (CNA) |
| Linux Linux | e96fbac8d3a73b0bc165383c092a30628561d320 | Vendor (CNA) |
| Linux Linux | fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa | Vendor (CNA) |
| azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 | 6.6.145.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.1.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0590 · Jul 21, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4a0bb0fd63fe2b0c62e1072cd1811d6f61e0081c
- git.kernel.org/stable/c/8daaf7f73fe998631a160d1a5a7e1b0b0480eef8
- git.kernel.org/stable/c/8de7b386ffad480ca59222b688c94a2da8f0d805
- git.kernel.org/stable/c/9901f847a762a5d953871dd95767ce2aed3d684d
- git.kernel.org/stable/c/d5616beb3355b5fca2280d796c1cf7ada4ee6551
- git.kernel.org/stable/c/e96fbac8d3a73b0bc165383c092a30628561d320
- git.kernel.org/stable/c/fc0c3b9cf27cfa2a06f66dae1d08c668fe0a2faa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.