Bluetooth: Fix responding to invalid L2CAP signaling commands
authorJohan Hedberg <johan.hedberg@intel.com>
Mon, 16 Sep 2013 10:05:18 +0000 (13:05 +0300)
committerGustavo Padovan <gustavo.padovan@collabora.co.uk>
Wed, 18 Sep 2013 21:50:53 +0000 (16:50 -0500)
commit69c4e4e8b4ca8440e5cbb66219a179e73f7b9e9a
tree30425e513743c92499c582a33997bb9d4d624ba3
parent9245e7375816c4d94d6327c8761b3c7431a5bc2f
Bluetooth: Fix responding to invalid L2CAP signaling commands

When we have an LE link we should not respond to any data on the BR/EDR
L2CAP signaling channel (0x0001) and vice-versa when we have a BR/EDR
link we should not respond to LE L2CAP (CID 0x0005) signaling commands.
This patch fixes this issue by checking for a valid link type and
ignores data if it is wrong.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
net/bluetooth/l2cap_core.c