Bluetooth: Prevent buffer overflow in l2cap config request
authorDan Rosenberg <drosenberg@vsecurity.com>
Fri, 24 Jun 2011 12:38:05 +0000 (08:38 -0400)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 7 Nov 2011 21:47:40 +0000 (13:47 -0800)
commitb847425fb436aca533a769cc15b4fa11d95177ee
tree07b8d43836f8709e9bc5714a4cf784b9862a7c41
parent643e2dfa4ff8ea1fab0b6f1e1e06cdfbfc0a703a
Bluetooth: Prevent buffer overflow in l2cap config request

commit 7ac28817536797fd40e9646452183606f9e17f71 upstream.

A remote user can provide a small value for the command size field in
the command header of an l2cap configuration request, resulting in an
integer underflow when subtracting the size of the configuration request
header.  This results in copying a very large amount of data via
memcpy() and destroying the kernel heap.  Check for underflow.

Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
net/bluetooth/l2cap.c