CVE-2026-90256

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.

Bluetooth L2CAP can hit a use after free because hci_conn::l2cap_data is read in l2cap_disconn_ind without the same locking used when l2cap_conn is deleted. A nearby Bluetooth peer or a local actor able to drive Bluetooth connection and disconnection timing may trigger the race while disc_work is processing a disconnect indication, causing l2cap_disconn_ind to read conn disc_reason from a freed l2cap_conn. For the CVSS the PR:N is used for the paranoid score because an adjacent Bluetooth attacker does not need an account or local privileges on the victim if the affected Bluetooth path is reachable. The issue is not Internet routable and should be treated as adjacent network reachable rather than AV:N. Impact is at least denial of service via kernel warning or crash. In worst case it may allow limited confidentiality or integrity impact due to a kernel UAF read pattern and should be reviewed manually.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.