From: syzbot <syzbot+80f5bab4eb14d14e7386@syzkaller.appspotmail.com>
To: anant.thazhemadam@gmail.com, davem@davemloft.net,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in mgmt_cmd_status
Date: Mon, 05 Apr 2021 10:34:18 -0700 [thread overview]
Message-ID: <0000000000007cfd9b05bf3d1b70@google.com> (raw)
In-Reply-To: <0000000000003798d705aedd870d@google.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+80f5bab4eb14d14e7386@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
prev parent reply other threads:[~2021-04-05 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:49 memory leak in mgmt_cmd_status syzbot
2021-04-05 17:34 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000007cfd9b05bf3d1b70@google.com \
--to=syzbot+80f5bab4eb14d14e7386@syzkaller.appspotmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.