From: syzbot <syzbot+a7db9083ed4017ba4423@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, sbrivio@redhat.com, sd@queasysnail.net,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: KASAN: use-after-free Read in _decode_session4
Date: Thu, 07 Nov 2019 05:42:04 -0800 [thread overview]
Message-ID: <000000000000af44bb0596c1d4e8@google.com> (raw)
In-Reply-To: <001a113fe6d081698f0568a5dcac@google.com>
syzbot suspects this bug was fixed by commit:
commit c6741fbed6dc0f183d26c4b6bca4517672f92e6c
Author: Stefano Brivio <sbrivio@redhat.com>
Date: Thu Mar 15 16:17:11 2018 +0000
vti6: Properly adjust vti6 MTU from MTU of lower device
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1710f0dc600000
start commit: 0b412605 Merge tag 'drm-fixes-for-v4.16-rc8' of git://peop..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8addcf4530d93e53
dashboard link: https://syzkaller.appspot.com/bug?extid=a7db9083ed4017ba4423
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14bf273b800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117045d3800000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: vti6: Properly adjust vti6 MTU from MTU of lower device
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-07 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 19:01 KASAN: use-after-free Read in _decode_session4 syzbot
2019-11-07 13:42 ` 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=000000000000af44bb0596c1d4e8@google.com \
--to=syzbot+a7db9083ed4017ba4423@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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).