Bluetooth: hci_h5: close serdev device and free hu in h5_close
authorAnant Thazhemadam <anant.thazhemadam@gmail.com>
Tue, 29 Sep 2020 18:58:15 +0000 (00:28 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 6 Jan 2021 13:56:51 +0000 (14:56 +0100)
commit 70f259a3f4276b71db365b1d6ff1eab805ea6ec3 upstream.

When h5_close() gets called, the memory allocated for the hu gets
freed only if hu->serdev doesn't exist. This leads to a memory leak.
So when h5_close() is requested, close the serdev device instance and
free the memory allocated to the hu entirely instead.

Fixes: https://syzkaller.appspot.com/bug?extid=6ce141c55b2f7aafd1c4
Reported-by: syzbot+6ce141c55b2f7aafd1c4@syzkaller.appspotmail.com
Tested-by: syzbot+6ce141c55b2f7aafd1c4@syzkaller.appspotmail.com
Signed-off-by: Anant Thazhemadam <anant.thazhemadam@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/bluetooth/hci_h5.c

index 78d635f..376164c 100644 (file)
@@ -251,8 +251,12 @@ static int h5_close(struct hci_uart *hu)
        if (h5->vnd && h5->vnd->close)
                h5->vnd->close(h5);
 
-       if (!hu->serdev)
-               kfree(h5);
+       if (hu->serdev)
+               serdev_device_close(hu->serdev);
+
+       kfree_skb(h5->rx_skb);
+       kfree(h5);
+       h5 = NULL;
 
        return 0;
 }