memory leak in mgmt_cmd_status

7 views
Skip to first unread message

syzbot

unread,
Sep 9, 2020, 4:49:24 AM9/9/20
to da...@davemloft.net, johan....@gmail.com, ku...@kernel.org, linux-b...@vger.kernel.org, linux-...@vger.kernel.org, mar...@holtmann.org, net...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6f6a73c8 Merge tag 'drm-fixes-2020-09-08' of git://anongit..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=152e3245900000
kernel config: https://syzkaller.appspot.com/x/.config?x=7954285d6e960c0f
dashboard link: https://syzkaller.appspot.com/bug?extid=80f5bab4eb14d14e7386
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16877335900000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+80f5ba...@syzkaller.appspotmail.com

2020/09/09 02:38:52 executed programs: 3
2020/09/09 02:38:58 executed programs: 5
2020/09/09 02:39:03 executed programs: 7
BUG: memory leak
unreferenced object 0xffff888119d41a00 (size 224):
comm "kworker/u5:0", pid 1520, jiffies 4294954656 (age 28.430s)
hex dump (first 32 bytes):
d0 30 1c 2b 81 88 ff ff d0 30 1c 2b 81 88 ff ff .0.+.....0.+....
00 00 00 00 00 00 00 00 00 30 1c 2b 81 88 ff ff .........0.+....
backtrace:
[<000000007a3b2b8a>] __alloc_skb+0x5e/0x250 net/core/skbuff.c:198
[<000000003fe180cd>] alloc_skb include/linux/skbuff.h:1094 [inline]
[<000000003fe180cd>] mgmt_cmd_status+0x31/0x140 net/bluetooth/mgmt_util.c:102
[<00000000a98852de>] mgmt_set_discoverable_complete+0x18e/0x1c0 net/bluetooth/mgmt.c:1351
[<000000000d6aa222>] discoverable_update_work+0x7a/0xa0 net/bluetooth/hci_request.c:2595
[<00000000159838c7>] process_one_work+0x213/0x4d0 kernel/workqueue.c:2269
[<0000000087b95ef0>] worker_thread+0x58/0x4b0 kernel/workqueue.c:2415
[<0000000059403542>] kthread+0x164/0x190 kernel/kthread.c:292
[<00000000d35ee226>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Apr 5, 2021, 1:34:19 PM4/5/21
to anant.th...@gmail.com, da...@davemloft.net, johan....@gmail.com, ku...@kernel.org, linux-b...@vger.kernel.org, linux-...@vger.kernel.org, luiz....@gmail.com, mar...@holtmann.org, net...@vger.kernel.org, syzkall...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: e49d033b Linux 5.12-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12579f11d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8dbd3c72fdc7777
dashboard link: https://syzkaller.appspot.com/bug?extid=80f5bab4eb14d14e7386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143b1696d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c5a30ed00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+80f5ba...@syzkaller.appspotmail.com

BUG: memory leak
unreferenced object 0xffff88810ddf4700 (size 232):
comm "kworker/u5:2", pid 8406, jiffies 4294997792 (age 10.670s)
hex dump (first 32 bytes):
d0 f0 af 0e 81 88 ff ff d0 f0 af 0e 81 88 ff ff ................
00 00 00 00 00 00 00 00 00 f0 af 0e 81 88 ff ff ................
backtrace:
[<ffffffff8364af8f>] __alloc_skb+0x20f/0x280 net/core/skbuff.c:412
[<ffffffff83c5f871>] alloc_skb include/linux/skbuff.h:1103 [inline]
[<ffffffff83c5f871>] mgmt_cmd_status+0x31/0x160 net/bluetooth/mgmt_util.c:102
[<ffffffff83c2a669>] mgmt_set_discoverable_complete+0x1b9/0x1e0 net/bluetooth/mgmt.c:1357
[<ffffffff83c579d8>] discoverable_update_work+0x88/0xb0 net/bluetooth/hci_request.c:2806
[<ffffffff812595d9>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2275
[<ffffffff81259ec9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2421
[<ffffffff812615f8>] kthread+0x178/0x1b0 kernel/kthread.c:292
[<ffffffff8100227f>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294


syzbot

unread,
Oct 10, 2022, 3:27:27 AM10/10/22
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages