Bluetooth: RFCOMM - Fix info leak in getsockopt(BT_SECURITY)
authorMathias Krause <minipli@googlemail.com>
Wed, 15 Aug 2012 11:31:48 +0000 (11:31 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 19 Sep 2012 14:04:51 +0000 (15:04 +0100)
commit1621af48f4c2cf3e10438507bea36af7189603b9
tree2dbb41a2b0f09ae37c69f09c94ad589fb369c6fd
parent1ec7005779d27fabc6fb64f0852745aaac4a66d2
Bluetooth: RFCOMM - Fix info leak in getsockopt(BT_SECURITY)

[ Upstream commit 9ad2de43f1aee7e7274a4e0d41465489299e344b ]

The RFCOMM code fails to initialize the key_size member of struct
bt_security before copying it to userland -- that for leaking one
byte kernel stack. Initialize key_size with 0 to avoid the info
leak.

Signed-off-by: Mathias Krause <minipli@googlemail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: Gustavo Padovan <gustavo@padovan.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
net/bluetooth/rfcomm/sock.c