+1
−0
+1
−0
+1
−0
Loading
When TX timestamping is enabled via SO_TIMESTAMPING, SKBs may be queued into sk_error_queue and will stay there until consumed. If userspace never gets to read the timestamps, or if the controller is removed unexpectedly, these SKBs will leak. Fix by adding skb_queue_purge() calls for sk_error_queue in affected bluetooth destructors. RFCOMM does not currently use sk_error_queue. Fixes: 134f4b39 ("Bluetooth: add support for skb TX SND/COMPLETION timestamping") Reported-by:<syzbot+7ff4013eabad1407b70a@syzkaller.appspotmail.com> Closes: https://syzbot.org/bug?extid=7ff4013eabad1407b70a Cc: stable@vger.kernel.org Signed-off-by:
Heitor Alves de Siqueira <halves@igalia.com> Signed-off-by:
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>