From: syzbot <syzbot+9276d76e83e3bcde6c99@syzkaller.appspotmail.com>
To: davem@davemloft.net, dvyukov@google.com, glider@google.com,
linux-kernel@vger.kernel.org, linux-sctp@vger.kernel.org,
lucien.xin@gmail.com, marcelo.leitner@gmail.com,
netdev@vger.kernel.org, nhorman@tuxdriver.com,
syzkaller-bugs@googlegroups.com, vyasevich@gmail.com
Subject: Re: KASAN: use-after-free Read in __lock_sock
Date: Wed, 10 Apr 2019 11:33:00 +0000 [thread overview]
Message-ID: <000000000000940af705862b6e90@google.com> (raw)
In-Reply-To: <000000000000b98a67057ad7158a@google.com>
syzbot has bisected this bug to:
commit 8f840e47f190cbe61a96945c13e9551048d42cef
Author: Xin Long <lucien.xin@gmail.com>
Date: Thu Apr 14 07:35:33 2016 +0000
sctp: add the sctp_diag.c file
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x1719585b200000
start commit: 0072a0c1 Merge tag 'media/v4.20-4' of git://git.kernel.org..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x\x1499585b200000
console output: https://syzkaller.appspot.com/x/log.txt?x\x1099585b200000
kernel config: https://syzkaller.appspot.com/x/.config?x¹cc5a440391cbfd
dashboard link: https://syzkaller.appspot.com/bug?extid’76d76e83e3bcde6c99
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x12b80cfb400000
Reported-by: syzbot+9276d76e83e3bcde6c99@syzkaller.appspotmail.com
Fixes: 8f840e47f190 ("sctp: add the sctp_diag.c file")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-10 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 7:18 KASAN: use-after-free Read in __lock_sock syzbot
2018-11-19 8:57 ` Xin Long
2018-11-22 13:13 ` Marcelo Ricardo Leitner
2018-11-22 13:44 ` Xin Long
2018-11-22 14:37 ` Marcelo Ricardo Leitner
2021-05-05 21:21 ` KASAN: use-after-free Read in __lock_sock (high-risk primitives found) SyzScope
2021-12-06 19:21 ` KASAN: use-after-free Read in __lock_sock Lee Jones
2018-12-05 18:32 ` syzbot
2018-12-06 7:20 ` Xin Long
2018-12-06 8:39 ` Dmitry Vyukov
2019-04-10 11:33 ` 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=000000000000940af705862b6e90@google.com \
--to=syzbot+9276d76e83e3bcde6c99@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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).