From: syzbot <syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com>
To: andreyknvl@google.com, dmg@turingmachine.org,
gregkh@linuxfoundation.org, johan@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in adu_disconnect
Date: Fri, 20 Sep 2019 07:58:00 -0700 [thread overview]
Message-ID: <000000000000d8c1ef0592fd4ba3@google.com> (raw)
In-Reply-To: <20190920143855.GS30545@localhost>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com
Tested on:
commit: e0bd8d79 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git
kernel config: https://syzkaller.appspot.com/x/.config?x=8847e5384a16f66a
dashboard link: https://syzkaller.appspot.com/bug?extid=0243cb250a51eeefb8cc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=122eb075600000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2019-09-20 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 11:58 KASAN: use-after-free Read in adu_disconnect syzbot
2019-08-09 20:24 ` syzbot
2019-09-19 10:35 ` Johan Hovold
2019-09-19 10:53 ` syzbot
2019-09-20 8:26 ` Johan Hovold
2019-09-20 9:02 ` syzbot
2019-09-20 9:08 ` Johan Hovold
2019-09-20 9:13 ` Dmitry Vyukov
2019-09-20 9:21 ` Johan Hovold
2019-09-20 9:28 ` Dmitry Vyukov
2019-09-20 9:35 ` Johan Hovold
2019-09-20 10:05 ` Dmitry Vyukov
2019-09-20 9:20 ` syzbot
2019-09-20 10:02 ` Johan Hovold
2019-09-20 10:08 ` Dmitry Vyukov
2019-09-20 10:16 ` Andrey Konovalov
2019-09-20 14:31 ` Johan Hovold
2019-09-20 10:21 ` syzbot
2019-09-20 14:38 ` Johan Hovold
2019-09-20 14:58 ` 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=000000000000d8c1ef0592fd4ba3@google.com \
--to=syzbot+0243cb250a51eeefb8cc@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=dmg@turingmachine.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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.