From: syzbot <syzbot+e918523f77e62790d6d9@syzkaller.appspotmail.com>
To: antony.antony@secunet.com, coreteam@netfilter.org,
davem@davemloft.net, eyal.birger@gmail.com, fw@strlen.de,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in nf_hook_entries_grow
Date: Mon, 17 Jan 2022 08:12:11 -0800 [thread overview]
Message-ID: <00000000000044c19b05d5c96a09@google.com> (raw)
In-Reply-To: <000000000000c0069f05d38f279d@google.com>
syzbot suspects this issue was fixed by commit:
commit 8dce43919566f06e865f7e8949f5c10d8c2493f5
Author: Antony Antony <antony.antony@secunet.com>
Date: Sun Dec 12 10:34:30 2021 +0000
xfrm: interface with if_id 0 should return error
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10eb9bb0700000
start commit: 9eaa88c7036e Merge tag 'libata-5.16-rc6' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=10f3f669b8093e95
dashboard link: https://syzkaller.appspot.com/bug?extid=e918523f77e62790d6d9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1781a643b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15130199b00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xfrm: interface with if_id 0 should return error
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-01-17 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 7:51 [syzbot] KASAN: use-after-free Read in nf_hook_entries_grow syzbot
2022-01-17 16:12 ` 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=00000000000044c19b05d5c96a09@google.com \
--to=syzbot+e918523f77e62790d6d9@syzkaller.appspotmail.com \
--cc=antony.antony@secunet.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eyal.birger@gmail.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.