From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+793a590957d9c1b96620@syzkaller.appspotmail.com>
Cc: ali.abdallah@suse.com, coreteam@netfilter.org,
davem@davemloft.net, edumazet@google.com, fw@strlen.de,
kadlec@netfilter.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, ozsh@nvidia.com,
pabeni@redhat.com, pablo@netfilter.org, paulb@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in nf_confirm
Date: Tue, 17 May 2022 21:47:51 +0200 [thread overview]
Message-ID: <20220517194751.GA4316@breakpoint.cc> (raw)
In-Reply-To: <000000000000fb4af305df391431@google.com>
syzbot <syzbot+793a590957d9c1b96620@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: d887ae3247e0 octeontx2-pf: Remove unnecessary synchronize_..
> git tree: net-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=17f2b659f00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=b1aab282dc5dd920
> dashboard link: https://syzkaller.appspot.com/bug?extid=793a590957d9c1b96620
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1313dce6f00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169eb59ef00000
>
> The issue was bisected to:
>
> commit 1397af5bfd7d32b0cf2adb70a78c9a9e8f11d912
> Author: Florian Westphal <fw@strlen.de>
> Date: Mon Apr 11 11:01:18 2022 +0000
>
> netfilter: conntrack: remove the percpu dying list
AFAICS this bug exists since
Fixes: 71d8c47fc653 ("netfilter: conntrack: introduce clash resolution on insertion race")
nf_confirm needs to re-fetch 'ct' from skb->_nfct. Will send a patch.
prev parent reply other threads:[~2022-05-17 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:12 [syzbot] KASAN: use-after-free Read in nf_confirm syzbot
2022-05-17 19:47 ` Florian Westphal [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=20220517194751.GA4316@breakpoint.cc \
--to=fw@strlen.de \
--cc=ali.abdallah@suse.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=ozsh@nvidia.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=paulb@nvidia.com \
--cc=syzbot+793a590957d9c1b96620@syzkaller.appspotmail.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.