Answer in brief
CVE-2026-89774 records a High severity (CVSS 8.8) vulnerability in Bluetooth: SCO: hold sk properly in sco_conn_ready. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=27c24fda62b601d6f9ca5e992502578c4310876f <50aae396dc30377bec8e3b181b8346f8fd38f7d8 || >=27c24fda62b601d6f9ca5e992502578c4310876f <6e3840578aaad1a296aab1eaaa89ea3b7d5cbae1 || >=27c24fda62b601d6f9ca5e992502578c4310876f <d141d9b769bcd1b747898528c5023270cda040f2 || >=27c24fda62b601d6f9ca5e992502578c4310876f <73cb063f5ec6ca51eb1e246c6d332563002ac277 || >=27c24fda62b601d6f9ca5e992502578c4310876f <7199c78c3a3e399a4dc439d845826793880ccedc || >=27c24fda62b601d6f9ca5e992502578c4310876f <4e37f6452d586b95c346a9abdd2fb80b67794f39 | 50aae396dc30377bec8e3b181b8346f8fd38f7d8, 6e3840578aaad1a296aab1eaaa89ea3b7d5cbae1, d141d9b769bcd1b747898528c5023270cda040f2, 73cb063f5ec6ca51eb1e246c6d332563002ac277, 7199c78c3a3e399a4dc439d845826793880ccedc, 4e37f6452d586b95c346a9abdd2fb80b67794f39 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.