Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 7197462e90b8ce15caa1ae15d4bc2bb8cd21b11e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free.
Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock.
Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.
From the CVE record · Linux
The Linux kernel's Bluetooth SCO receive path can access a socket after it has been freed. This can happen when a concurrent close frees the socket after sco_recv_frame() releases its lock; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the affected Bluetooth SCO code should check their versions; affected versions were not provided.