In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: hold sk properly in iso_conn_ready sk deref in iso_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk is currently accessed without either: [Task 1] [Task 2] iso_sock_release iso_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) iso_sock_kill(sk) UAF on sk deref Fix possible UAF by holding sk refcount in iso_conn_ready(). Also recheck after lock_sock that the socket is still valid. Adjust locking so conn->sk is cleared only under lock_sock.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-21 12:45
- References+2 references (now 5)NVD modified 2026-10-21 13:19
- StatusPublished → ReceivedNVD modified 2026-10-21 13:19
- StatusReceived → PublishedNVD modified 2026-10-21 12:45
- First seenCVSS 8.8NVD modified 2026-10-16 20:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/0d255e63fcf3f13a570d7ac11678fa1164ac015c
- https://git.kernel.org/stable/c/1308d72903d792d10b82bc4ef08b8a4452308b04
- https://git.kernel.org/stable/c/44590dc53c9e949d2fed399a571a89c3d7d0b245
- https://git.kernel.org/stable/c/4e9b5e8669b3602a4e01b6d1e9539b72e42c84d5
- https://git.kernel.org/stable/c/99b65f0ea3370c13687ff870330c425b6ca44e89