Linux
Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < 1702f12cf59a1c3b670eb6bb4a4d6fcccf07e3b8
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < d47b8f8c02a3d3f282693e5a4ff1f6b4b00518de
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < 2387cd06a2c0b416f05028b02bba1089f54c28d9
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < 49fd7116f76b860b230843700fb7423ab5331e1f
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < 03288b7447c9e572f8ab82fc29cfb4ca719ab210
- >= ccf74f2390d60a2f9a75ef496d2564abb478f46a, < 560bef609fa5992745929e8d7d458b9d88dd2830
Fixed in 1702f12cf59a1c3b670eb6bb4a4d6fcccf07e3b8, d47b8f8c02a3d3f282693e5a4ff1f6b4b00518de, 2387cd06a2c0b416f05028b02bba1089f54c28d9, 49fd7116f76b860b230843700fb7423ab5331e1f, 03288b7447c9e572f8ab82fc29cfb4ca719ab210, 560bef609fa5992745929e8d7d458b9d88dd2830
- 6.0
Fixed in 0, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to 1702f12cf59a1c3b670eb6bb4a4d6fcccf07e3b8 or d47b8f8c02a3d3f282693e5a4ff1f6b4b00518de or 2387cd06a2c0b416f05028b02bba1089f54c28d9 or 49fd7116f76b860b230843700fb7423ab5331e1f or 03288b7447c9e572f8ab82fc29cfb4ca719ab210 or 560bef609fa5992745929e8d7d458b9d88dd2830 or later.
Upgrade Linux to 0 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationFirst public PoC 66 days after publication; not in CISA KEV. First PoC: nanhang-950/CVE-2026-80914-POC (created 14 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| nanhang-950/CVE-2026-80914-POC | 14 Nov 2026 +66 d | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.