This is a note to let you know that I've just added the patch titled Bluetooth: btusb: Fix memory leak in Intel setup routine to the 4.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: bluetooth-btusb-fix-memory-leak-in-intel-setup-routine.patch and it can be found in the queue-4.1 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let <stable@xxxxxxxxxxxxxxx> know about it. >From ecffc80478cdce122f0ecb6a4e4f909132dd5c47 Mon Sep 17 00:00:00 2001 From: Marcel Holtmann <marcel@xxxxxxxxxxxx> Date: Sun, 7 Jun 2015 09:42:19 +0200 Subject: Bluetooth: btusb: Fix memory leak in Intel setup routine From: Marcel Holtmann <marcel@xxxxxxxxxxxx> commit ecffc80478cdce122f0ecb6a4e4f909132dd5c47 upstream. The SKB returned from the Intel specific version information command is missing a kfree_skb. Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> --- drivers/bluetooth/btusb.c | 2 ++ 1 file changed, 2 insertions(+) --- a/drivers/bluetooth/btusb.c +++ b/drivers/bluetooth/btusb.c @@ -1993,6 +1993,8 @@ static int btusb_setup_intel(struct hci_ } fw_ptr = fw->data; + kfree_skb(skb); + /* This Intel specific command enables the manufacturer mode of the * controller. * Patches currently in stable-queue which might be from marcel@xxxxxxxxxxxx are queue-4.1/bluetooth-btusb-correct-typo-in-roper-class-1-bluetooth-dongle.patch queue-4.1/bluetooth-btusb-fix-secure-send-command-length-alignment-on-intel-8260.patch queue-4.1/bluetooth-btbcm-allow-btbcm_read_verbose_config-to-fail-on-apple.patch queue-4.1/ieee802154-fix-sockaddr_ieee802154-implicit-padding-information-leak.patch queue-4.1/bluetooth-btusb-fix-memory-leak-in-intel-setup-routine.patch queue-4.1/bluetooth-fix-race-condition-with-user-channel-and-setup-stage.patch -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html