Bluetooth: call sock_hold earlier in sco_conn_del
[ Upstream commit f4712fa993
]
In sco_conn_del, conn->sk is read while holding on to the
sco_conn.lock to avoid races with a socket that could be released
concurrently.
However, in between unlocking sco_conn.lock and calling sock_hold,
it's possible for the socket to be freed, which would cause a
use-after-free write when sock_hold is finally called.
To fix this, the reference count of the socket should be increased
while the sco_conn.lock is still held.
Signed-off-by: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
Родитель
7e22e4db95
Коммит
a05a18cfbf
|
@ -187,10 +187,11 @@ static void sco_conn_del(struct hci_conn *hcon, int err)
|
|||
/* Kill socket */
|
||||
sco_conn_lock(conn);
|
||||
sk = conn->sk;
|
||||
if (sk)
|
||||
sock_hold(sk);
|
||||
sco_conn_unlock(conn);
|
||||
|
||||
if (sk) {
|
||||
sock_hold(sk);
|
||||
lock_sock(sk);
|
||||
sco_sock_clear_timer(sk);
|
||||
sco_chan_del(sk, err);
|
||||
|
|
Загрузка…
Ссылка в новой задаче