Bluetooth: L2CAP: Fix potential user-after-free
[ Upstream commit df5703348813235874d851934e957c3723d71644 ]
This fixes all instances of which requires to allocate a buffer calling
alloc_skb which may release the chan lock and reacquire later which
makes it possible that the chan is disconnected in the meantime.
Fixes: a6a5568c03
("Bluetooth: Lock the L2CAP channel when sending")
Reported-by: Alexander Coffin <alex.coffin@matician.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:

committed by
Greg Kroah-Hartman

parent
4f4c970a05
commit
b8ed41cc04
@@ -1623,6 +1623,14 @@ static struct sk_buff *l2cap_sock_alloc_skb_cb(struct l2cap_chan *chan,
|
||||
if (!skb)
|
||||
return ERR_PTR(err);
|
||||
|
||||
/* Channel lock is released before requesting new skb and then
|
||||
* reacquired thus we need to recheck channel state.
|
||||
*/
|
||||
if (chan->state != BT_CONNECTED) {
|
||||
kfree_skb(skb);
|
||||
return ERR_PTR(-ENOTCONN);
|
||||
}
|
||||
|
||||
skb->priority = sk->sk_priority;
|
||||
|
||||
bt_cb(skb)->l2cap.chan = chan;
|
||||
|
Reference in New Issue
Block a user