CVE-2026-90256

Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind

Published Sep 17, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability is a Use After Free error in the Linux kernel Bluetooth L2CAP subsystem. When a connection is discarded through a timeout, the kernel accesses the l2cap_data structure without holding the proper lock. If the connection is concurrently deleted, the data structure is freed while still being referenced, which can crash the kernel or allow an attacker to execute arbitrary code with kernel privileges. This flaw corresponds to a classic UAF weakness and carries a high severity of CVSS 8.8.

Affected Systems

All Linux kernel builds that include the Bluetooth L2CAP stack are potentially affected, as the vulnerability is present in generic Linux kernel code. No specific version range is supplied in the advisory, so any kernel lacking the fix should be considered vulnerable. Users of distributions that ship customized kernels should verify whether similar code paths exist.

Risk and Exploitability

The CVSS score of 8.8 indicates high severity, while the EPSS score of < 1% suggests exploitation is currently rare and unlikely in the wild. The vulnerability is not listed in the CISA KEV catalog, further indicating it is not a widely exploited threat. The most likely attack vector is local, involving an attacker who can trigger Bluetooth operations on a system they can control, or possibly a remote entity that can present a spoofed Bluetooth device to cause a race condition. Because the bug requires a timing race, exploitation may require significant effort.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes the commit that introduces proto_lock around l2cap_data operations.
  • If an immediate kernel upgrade cannot be performed, disable the Bluetooth subsystem or the specific L2CAP functionality until the patch is applied.
  • Monitor vendor and distribution advisories for kernel updates that address this flaw and apply them promptly.

Generated by OpenCVE AI on September 20, 2026 at 03:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9173-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9175-1 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
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.
Title Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 21, 2026, 12:50 PM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 21, 2026, 1:20 PM