From: syzbot <syzbot+e736399a2c4054612307@syzkaller.appspotmail.com>
To: 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, ebiggers3@gmail.com,
herbert@gondor.apana.org.au, jason@zx2c4.com,
john.fastabend@gmail.com, k.marinushkin@gmail.com,
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, 21 Mar 2019 02:33:00 -0700 [thread overview]
Message-ID: <0000000000009e8ef30584976ca9@google.com> (raw)
In-Reply-To: <00000000000060e0ae057a092be8@google.com>
syzbot has bisected this bug to:
commit 428490e38b2e352812e0b765d8bceafab0ec441d
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date: Wed Sep 20 14:58:39 2017 +0000
security/keys: rewrite all of big_key crypto
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=160eabcf200000
start commit: 428490e3 security/keys: rewrite all of big_key crypto
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=150eabcf200000
console output: https://syzkaller.appspot.com/x/log.txt?x=110eabcf200000
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
Reported-by: syzbot+e736399a2c4054612307@syzkaller.appspotmail.com
Fixes: 428490e38b2e ("security/keys: rewrite all of big_key crypto")
next prev parent reply other threads:[~2019-03-21 9:33 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 [this message]
2019-04-23 20:04 ` Kees Cook
2019-11-07 13:42 ` syzbot
2019-11-07 20:05 ` Jakub Kicinski
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=0000000000009e8ef30584976ca9@google.com \
--to=syzbot+e736399a2c4054612307@syzkaller.appspotmail.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=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=k.marinushkin@gmail.com \
--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=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).