CVE-2026-89774
CVE CVE-2026-89774EUVD EUVD-2026-80255Published 2026-09-16T08:24:21.000ZLast changed 2026-09-16T14:38:26.000ZCVSS 8.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: hold sk properly in sco_conn_ready sk deref in sco_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk and parent sk is currently accessed without either, and without checking parent->sk_state: [Task 1] [Task 2] sco_sock_release sco_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) sco_sock_kill(sk) UAF on sk deref and similarly for access to sco_get_sock_listen() return value. Fix possible UAF by holding sk refcount in sco_conn_ready() and making sco_get_sock_listen() increase refcount. Also recheck after lock_sock that the socket is still valid. Adjust conn->sk locking so it's protected also by lock_sock() of the associated socket if any.
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 patch: 5.15.212; 27c24fda62b601d6f9ca5e992502578c4310876f <7199c78c3a3e399a4dc439d845826793880ccedc; 27c24fda62b601d6f9ca5e992502578c4310876f <73cb063f5ec6ca51eb1e246c6d332563002ac277; patch: 6.12.97; 27c24fda62b601d6f9ca5e992502578c4310876f <50aae396dc30377bec8e3b181b8346f8fd38f7d8; patch: 6.1.178; patch: 0; patch: 7.1; 5.15; patch: 6.18.40; 27c24fda62b601d6f9ca5e992502578c4310876f <d141d9b769bcd1b747898528c5023270cda040f2; patch: 6.6.145; 27c24fda62b601d6f9ca5e992502578c4310876f <6e3840578aaad1a296aab1eaaa89ea3b7d5cbae1; 27c24fda62b601d6f9ca5e992502578c4310876f <4e37f6452d586b95c346a9abdd2fb80b67794f39
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 daysPatchlage 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.