From: syzbot <syzbot+7dd7f2f77a7a01d1dc14@syzkaller.appspotmail.com>
To: abhishekpandit@chromium.org, alainm@chromium.org,
davem@davemloft.net, johan.hedberg@gmail.com,
johan.hedberg@intel.com, josua.mayer@jm0.eu,
jukka.rissanen@linux.intel.com, keescook@chromium.org,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, marcel@holtmann.org,
mcchou@chromium.org, mike@foundries.io, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in refcount_warn_saturate
Date: Fri, 04 Sep 2020 07:44:09 -0700 [thread overview]
Message-ID: <000000000000c8101605ae7de686@google.com> (raw)
In-Reply-To: <00000000000055e1a9059f9e169f@google.com>
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
next prev parent reply other threads:[~2020-09-04 14:44 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 ` syzbot [this message]
2020-11-11 13:25 ` KASAN: use-after-free Write in refcount_warn_saturate Dmitry Vyukov
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=000000000000c8101605ae7de686@google.com \
--to=syzbot+7dd7f2f77a7a01d1dc14@syzkaller.appspotmail.com \
--cc=abhishekpandit@chromium.org \
--cc=alainm@chromium.org \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=johan.hedberg@intel.com \
--cc=josua.mayer@jm0.eu \
--cc=jukka.rissanen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=mike@foundries.io \
--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.