CVE-2026-90093

CVE CVE-2026-90093EUVD EUVD-2026-81954Published 2026-09-17T16:06:06.000ZLast changed 2026-09-18T17:52:59.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 7.1.4 <7.2; 7.2; 91047a4396a8b1857a6f712a90cf33ec0012b189; 5.15.216 <5.16; 8f90405a4a6f1f1880dc07996b47bf57c712bd8a; 0b0e2bf39cf99e458d991b9df253727e036a7d7d; 6.12.97 <6.13; 6.18.39 <6.19; patch: 7.3-rc1; 32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b; 50c38d9f42a529691e4e67ea9cedf4f0bfc8d277; d3b739db5dc6f688a60d56da872fabaf65246032; 6.1.183 <6.2; 6.6.145 <6.7; 5.10.265 <5.11; patch: 7.2.6; b66774b48dd98f07254951f74ea6f513efe7ff8b <f49321c85785178214fd67f2e9b4b73d6363783b; 8922c7940bae9ce4b1736dddb6362370793835c2; b66774b48dd98f07254951f74ea6f513efe7ff8b <ca2c4c26498643f421d35ffe258fafbd3ed461c3; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.