Answer in brief
CVE-2026-80914 records a Unknown severity vulnerability in Bluetooth: ISO: fix use-after-free of listener socket in iso_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.
A CVSS score is not reported in the current record. 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 | >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <2387cd06a2c0b416f05028b02bba1089f54c28d9 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <49fd7116f76b860b230843700fb7423ab5331e1f || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <03288b7447c9e572f8ab82fc29cfb4ca719ab210 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <560bef609fa5992745929e8d7d458b9d88dd2830 | 2387cd06a2c0b416f05028b02bba1089f54c28d9, 49fd7116f76b860b230843700fb7423ab5331e1f, 03288b7447c9e572f8ab82fc29cfb4ca719ab210, 560bef609fa5992745929e8d7d458b9d88dd2830 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 9, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready iso_conn_ready() looks up the BIS listener socket with iso_get_sock(), which takes a reference, and then, without re-checking its state, creates a child socket from it: parent = iso_get_sock(hdev, ...); if (!parent) return; lock_sock(parent); sk = iso_sock_alloc(sock_net(parent), NULL, BTPROTO_ISO, ...); ... iso_chan_add(conn, sk, parent); ... release_sock(parent); sock_put(parent); If the listener socket is closed concurrently, between iso_get_sock() and lock_sock(), the reference taken by iso_get_sock() may be the last one: the close path drops the link-list reference, and once iso_conn_ready() drops its own reference at the end of the function the socket is freed. The child socket, however, is already linked to the freed parent, and a later disconnect of the child runs iso_chan_del() -> bt_accept_unlink(), which dereferences the dangling parent pointer into the freed accept queue (a use-after-free). The same dangling pointer is also dereferenced through parent->***() in iso_chan_del(). Fix it the same way the connected (non-BIS) path was fixed in commit 0d255e63fcf3 ("Bluetooth: ISO: hold sk properly in iso_conn_ready"): after taking the socket lock, re-check that the parent is still a listening, alive socket, and bail out otherwise.
Quoted source text, attributed separately from HOL analysis.