From: syzbot <syzbot+5be8aebb1b7dfa90ef31@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
kuba@kernel.org, linux-kernel@vger.kernel.org,
lucien.xin@gmail.com, marcelo.leitner@gmail.com,
netdev@vger.kernel.org, steffen.klassert@secunet.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in decode_session6
Date: Sat, 31 Oct 2020 22:40:11 -0700 [thread overview]
Message-ID: <0000000000002d865a05b3051076@google.com> (raw)
In-Reply-To: <00000000000013259505a931dd26@google.com>
syzbot has bisected this issue to:
commit bcd623d8e9fa5f82bbd8cd464dc418d24139157b
Author: Xin Long <lucien.xin@gmail.com>
Date: Thu Oct 29 07:05:05 2020 +0000
sctp: call sk_setup_caps in sctp_packet_transmit instead
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14df9cb8500000
start commit: 68bb4665 Merge branch 'l2-multicast-forwarding-for-ocelot-..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16df9cb8500000
console output: https://syzkaller.appspot.com/x/log.txt?x=12df9cb8500000
kernel config: https://syzkaller.appspot.com/x/.config?x=eac680ae76558a0e
dashboard link: https://syzkaller.appspot.com/bug?extid=5be8aebb1b7dfa90ef31
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11286398500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bbf398500000
Reported-by: syzbot+5be8aebb1b7dfa90ef31@syzkaller.appspotmail.com
Fixes: bcd623d8e9fa ("sctp: call sk_setup_caps in sctp_packet_transmit instead")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-01 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 4:55 KASAN: use-after-free Read in decode_session6 syzbot
2020-10-31 16:43 ` syzbot
2020-11-01 5:40 ` syzbot [this message]
2020-11-03 13:14 ` Xin Long
2020-11-03 13:52 ` Xin Long
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=0000000000002d865a05b3051076@google.com \
--to=syzbot+5be8aebb1b7dfa90ef31@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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 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.