CVE-2026-90091

CVE CVE-2026-90091EUVD EUVD-2026-81952Published 2026-09-17T16:06:05.000ZLast changed 2026-09-18T17:52:56.000ZCVSS 8.0

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan For L2CAP sockets without owning sk->sk_socket, reading l2cap_pi(sk)->chan may race against concurrent l2cap_sock_kill() -> l2cap_sock_put_chan(). This excludes simultaneous proto_ops callbacks, but access in l2cap_sock_cleanup_listen() has unsafe lockless read. [Task 1] [Task 2 (hdev->workqueue)] l2cap_sock_release(parent) l2cap_disconn_cfm l2cap_sock_cleanup_listen l2cap_conn_del bt_accept_dequeue l2cap_chan_del lock_sock(sk) l2cap_sock_teardown_cb bt_accept_unlink bt_sk(sk)->parent = NULL release_sock(sk) ----------------> lock_sock(sk) parent = /* NULL */ lock_sock(sk) <--------------------- release_sock(sk) sock_set_flag(sk, SOCK_ZAPPED) l2cap_sock_close_cb l2cap_sock_kill(sk) l2cap_sock_put_chan chan = READ l2cap_pi(sk)->chan l2cap_pi(sk)->chan = NULL l2cap_chan_hold_unless_zero l2cap_put_chan(chan) kref_get_unless_zero(&chan->ref) Task 1 may observe NULL which causes null-ptr-deref. Fix the race by taking lock_sock() in l2cap_sock_kill() to synchronize with l2cap_sock_cleanup_listen(). hold_unless_zero() is not needed here, l2cap_pi(sk)->chan owns reference if it is non-NULL. Clarify code comments vs. locking.

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 6.1.178 <6.1.188; 6.18.40 <6.18.52; 36da806f7fbaee56ad9e81859deec203f9728700 <61d5ddbd524c715b224cbe7e9f01da4e05098b19; 8c37e4338c801ebb8cee52436c01c41e009f6e87 <7c7ac736b50fa259ed1bdddc18d79523f07c0442; 6.12.97 <6.12.110; patch: 6.1.188; 6fef032af0092ed5ccb767239a9ac1bc38c08a40 <66d6ef18548ae6d7dd452b84115fc82c0a73a4ea; 6fef032af0092ed5ccb767239a9ac1bc38c08a40 <32a7bc6e93be36b37fe61f351d312d358195bd61; b39298044e5534612511a2ff5de03ba5f6e7a820 <827de6bd2865b22aaabd554540def3b8a33018ab; 84e718b6a814edc84159361f9f454a4e92ae91ae <4f8c63fe0097c9f6ea34409f82f79b3894903d91; patch: 6.18.52; patch: 0; patch: 7.3-rc1; 6.6.145 <6.6.157; patch: 7.2.6; patch: 6.12.110; 733e76e74e406c1d1ddc7369420dd8a47f48bb8a; 7.1.5 <7.2; patch: 6.6.157; 7.2

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.