Bluetooth: ISO: fix UAF in iso_recv_frame
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ccf74f2390d60a2f9a75ef496d2564abb478f46a · < 47f23a259517abbdb8032c057a1e8a6bf3734878| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: ISO: fix UAF in iso_recv_frame
iso_recv_frame reads conn->sk under iso_conn_lock but releases the lock before using sk, with no reference held. A concurrent iso_sock_kill() can free sk in that window, causing use-after-free on sk->sk_state and sock_queue_rcv_skb().
Fix by replacing the bare pointer read with iso_sock_hold(conn), which calls sock_hold() while the spinlock is held, atomically elevating the refcount before the lock drops. Add a drop_put label so sock_put() is called on all exit paths where the hold succeeded.
From the CVE record · Linux
The Linux kernel's iso_recv_frame uses a socket after releasing the lock that protects its pointer, without holding a reference. If iso_sock_kill runs concurrently and frees the socket, this can cause a use-after-free. The input does not specify attacker access or user-interaction requirements.
Teams running Linux kernels with the affected Bluetooth ISO code should check their versions against the vendor advisory; affected versions are not specified in the input.