CVE-2026-64557Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()
- 8.8HighCVSS base score
- 0.29%Exploitation in 30 daysEPSS · top 78% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb() l2cap_sock_new_connection_cb() returned l2cap_pi(sk)->chan after release_sock(parent). Once the parent lock is dropped the newly enqueued child socket sk is reachable via the accept queue, so another task can accept and free it before the callback dereferences sk, resulting in a use-after-free. Rework the ->new_connection() op so the core, rather than the callback, owns the child channel's lifetime. The op now receives a pre-allocated new_chan and returns an errno instead of allocating and returning a channel. l2cap_new_connection() allocates the child channel and links it into the conn list via __l2cap_chan_add() before invoking the callback, so the conn-list reference keeps the channel alive once release_sock(parent) exposes the socket to other tasks. Channel configuration that was duplicated in l2cap_sock_init() and the various new_connection callbacks is consolidated into l2cap_chan_set_defaults(), which now inherits from the parent channel when one is supplied.
Timeline
ID reserved
By Linux
- 10 days later
· 10 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.29% · top 78% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < b39298044e5534612511a2ff5de03ba5f6e7a820
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < 8c37e4338c801ebb8cee52436c01c41e009f6e87
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < 84e718b6a814edc84159361f9f454a4e92ae91ae
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < 36da806f7fbaee56ad9e81859deec203f9728700
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < 733e76e74e406c1d1ddc7369420dd8a47f48bb8a
- affected 8ffb929098a56939ac71509302eeab5b207bf262 – < 6fef032af0092ed5ccb767239a9ac1bc38c08a40
- affected 3.13
- unaffected < 3.13
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b39298044e5534612511a2ff5de03ba5f6e7a820 (opens in a new tab)
- https://git.kernel.org/stable/c/8c37e4338c801ebb8cee52436c01c41e009f6e87 (opens in a new tab)
- https://git.kernel.org/stable/c/84e718b6a814edc84159361f9f454a4e92ae91ae (opens in a new tab)
- https://git.kernel.org/stable/c/36da806f7fbaee56ad9e81859deec203f9728700 (opens in a new tab)
- https://git.kernel.org/stable/c/733e76e74e406c1d1ddc7369420dd8a47f48bb8a (opens in a new tab)
- https://git.kernel.org/stable/c/6fef032af0092ed5ccb767239a9ac1bc38c08a40 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-50202 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64557)Record last updated .