From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: syzbot <syzbot+e736399a2c4054612307@syzkaller.appspotmail.com>
Cc: Jason@zx2c4.com, ard.biesheuvel@linaro.org, aviadye@mellanox.com,
borisp@mellanox.com, daniel@iogearbox.net, davejwatson@fb.com,
davem@davemloft.net, dhowells@redhat.com,
dirk.vandermerwe@netronome.com, ebiggers3@gmail.com,
herbert@gondor.apana.org.au, john.fastabend@gmail.com,
k.marinushkin@gmail.com, keescook@chromium.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, security@kernel.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in crypto_gcm_init_common
Date: Thu, 7 Nov 2019 15:05:18 -0500 [thread overview]
Message-ID: <20191107150518.36b4a872@cakuba.netronome.com> (raw)
In-Reply-To: <000000000000dd9f160596c1d465@google.com>
On Thu, 07 Nov 2019 05:42:07 -0800, syzbot wrote:
> syzbot suspects this bug was fixed by commit:
>
> commit 9354544cbccf68da1b047f8fb7b47630e3c8a59d
> Author: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
> Date: Mon Jun 24 04:26:58 2019 +0000
>
> net/tls: fix page double free on TX cleanup
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=168ad3c2600000
> start commit: 4710e789 Merge tag 'nfs-for-4.20-2' of git://git.linux-nfs..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=9384ecb1c973baed
> dashboard link: https://syzkaller.appspot.com/bug?extid=e736399a2c4054612307
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17902f5b400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111377e5400000
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: net/tls: fix page double free on TX cleanup
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
The bug report looks fairly strange and could indicate a double free,
but I don't see an entirely clear connection. We are double freeing a
record and its pages while the splat is from a slab-32.. Given the
bisection I think it's probably okay:
#syz fix: net/tls: fix page double free on TX cleanup
prev parent reply other threads:[~2019-11-07 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 1:38 KASAN: use-after-free Read in crypto_gcm_init_common syzbot
2018-11-07 7:26 ` Ard Biesheuvel
2018-11-07 7:26 ` Ard Biesheuvel
2019-03-21 9:33 ` syzbot
2019-04-23 20:04 ` Kees Cook
2019-11-07 13:42 ` syzbot
2019-11-07 20:05 ` Jakub Kicinski [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=20191107150518.36b4a872@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=Jason@zx2c4.com \
--cc=ard.biesheuvel@linaro.org \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dirk.vandermerwe@netronome.com \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=k.marinushkin@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+e736399a2c4054612307@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 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).