Bug 2536720 (CVE-2026-90256) - CVE-2026-90256 kernel: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
Summary: CVE-2026-90256 kernel: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix...
Keywords:
Status: NEW
Alias: CVE-2026-90256
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 19:19 UTC by OSIDB Bzimport
Modified: 2026-10-13 13:34 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 19:19:11 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.