Bluetooth: SCO: hold sk properly in sco_conn_ready
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 27c24fda62b601d6f9ca5e992502578c4310876f · < 4e37f6452d586b95c346a9abdd2fb80b67794f39| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SCO: hold sk properly in sco_conn_ready
sk deref in sco_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk and parent sk is currently accessed without either, and without checking parent->sk_state:
[Task 1] [Task 2] sco_sock_release sco_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) sco_sock_kill(sk) UAF on sk deref
and similarly for access to sco_get_sock_listen() return value.
Fix possible UAF by holding sk refcount in sco_conn_ready() and making sco_get_sock_listen() increase refcount. Also recheck after lock_sock that the socket is still valid. Adjust conn->sk locking so it's protected also by lock_sock() of the associated socket if any.
From the CVE record · Linux
The Linux kernel’s Bluetooth SCO code can dereference a socket after it is freed if a connection-ready operation races with socket closure. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Operators running Linux kernels with Bluetooth SCO support should check whether their kernel includes the fix; affected versions are not specified.