Linux Kernel Bluetooth stack Vulnerability Rated 7.8 CVSS

Last refreshed2026-10-15

Status: UPDATED | Advisory ID: CVE-2026-90093

Key Details

CVE	CVE-2026-90093
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-15
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Exploitation prediction (EPSS)	0.17% probability of exploitation in the next 30 days (5% percentile) -- FIRST.org's EPSS model.

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: access chan->conn safely in get/setsockopt

Since commit b66774b48dd9 ("Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref")

l2cap_chan::conn has held reference and remains non-NULL also after the

corresponding hci_conn is deleted. In this state accessing various

fields eg. hci_conn::hdev is invalid, which leads to KASAN crash in

l2cap_sock_setsockopt() access of conn->hcon->hdev.

Check l2cap_chan::conn.hcon corresponds to an alive hci_conn before

trying to use it in l2cap_sock.c. Hold l2cap_chan_lock() in

getsockopt/setsockopt to ensure it stays alive, and to avoid data races

in l2cap_chan fields. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-90093
CVE	https://www.cve.org/CVERecord?id=CVE-2026-90093

Source

Reference

NVD

CVE