Bluetooth: ISO: hold sk properly in iso_conn_ready
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 27c24fda62b601d6f9ca5e992502578c4310876f · < 0d255e63fcf3f13a570d7ac11678fa1164ac015c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's Bluetooth ISO code can dereference a socket after it has been freed if a socket closes concurrently with iso_conn_ready. This can cause a use-after-free; the input does not establish an attack path or authentication requirements.
Engineers running Linux kernels with Bluetooth ISO support should check their kernel versions; affected versions were not provided.