# CVE-2026-90256: linux: In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: use proto_lock for l2cap_data...

CVE-2026-90256 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-90256, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-90256
- Priority: High
- CVSS: 8.8 (high)
- EPSS: 0.0032
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Sep 17, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind  hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via hci_conn_timeout (disc_work) -> hci_proto_disconn_ind -> l2cap_disconn_ind.  This is UAF if the l2cap_conn is deleted concurrently.  disc_work is disabled sync in hci_conn_del(), so we cannot take hci_dev_lock in disc_work.  Fix by using proto_lock to guard l2cap_data, in addition to hdev->lock which is held in other access paths.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2026-90256](https://patchblox.com/security/data/fix/linux/debian-cve-2026-90256.md) | Sep 23, 2026 |
| Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-90256](https://patchblox.com/security/data/fix/linux/debian-cve-2026-90256.md) | Sep 23, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.