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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 2 Oct 2012 17:29:36 +0000 (10:29 -0700)
commit745dcdb0fd330f0cc984bd8a7764a81f04e44780
treef0acac1ff978f33ebb9fa23bb470d18e375a30df
parent639edee79eb2035b6fe3976f50a1c5364acc7352
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/bluetooth/rfcomm/sock.c