All reports
Medium

kernel: Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-90256

Probability of exploitation in the next 30 days: 0.32%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component. A use-after-free (UAF) vulnerability can occur when hci_conn::l2cap_data is accessed without proper locking during the disconnection indication process. This can lead to a system crash or potentially allow an attacker to execute arbitrary code.