From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+7dd7f2f77a7a01d1dc14@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: KASAN: use-after-free Write in refcount_warn_saturate
Date: Wed, 11 Nov 2020 14:25:21 +0100 [thread overview]
Message-ID: <CACT4Y+ak0Enm0CZ5rmUwyWRDkityJx9yzp1yyVDx2shpC5tL_A@mail.gmail.com> (raw)
In-Reply-To: <000000000000c8101605ae7de686@google.com>
On Fri, Sep 4, 2020 at 4:44 PM syzbot
<syzbot+7dd7f2f77a7a01d1dc14@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit b83764f9220a4a14525657466f299850bbc98de9
> Author: Miao-chen Chou <mcchou@chromium.org>
> Date: Tue Jun 30 03:15:00 2020 +0000
>
> Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f92e3e900000
> start commit: c0842fbc random32: move the pseudo-random 32-bit definitio..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=cf567e8c7428377e
> dashboard link: https://syzkaller.appspot.com/bug?extid=7dd7f2f77a7a01d1dc14
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b606dc900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=123e87cc900000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: Bluetooth: Fix kernel oops triggered by hci_adv_monitors_clear()
prev parent reply other threads:[~2020-11-11 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 7:50 KASAN: use-after-free Write in refcount_warn_saturate syzbot
2020-07-06 3:32 ` use-after-free in Bluetooth: 6lowpan (was Re: KASAN: use-after-free Write in refcount_warn_saturate) Kees Cook
2020-07-08 17:36 ` Ing. Josua Mayer
2020-09-04 14:44 ` KASAN: use-after-free Write in refcount_warn_saturate syzbot
2020-11-11 13:25 ` Dmitry Vyukov [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=CACT4Y+ak0Enm0CZ5rmUwyWRDkityJx9yzp1yyVDx2shpC5tL_A@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+7dd7f2f77a7a01d1dc14@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).