From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+257f413f0ea433750ffaa72b2748289380957904@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in crypto_chacha20_crypt
Date: Wed, 29 Nov 2017 00:57:47 -0800 [thread overview]
Message-ID: <20171129085747.GA20992@zzz.localdomain> (raw)
In-Reply-To: <94eb2c111b8c32eea2055f0c983c@google.com>
On Tue, Nov 28, 2017 at 07:23:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 1ea8d039f9edcfefb20d8ddfe136930f6e551529
> git://git.cmpxchg.org/linux-mmots.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> for information about syzkaller reproducers
>
>
> ==================================================================
> BUG: KASAN: use-after-free in __le32_to_cpup
> include/uapi/linux/byteorder/little_endian.h:58 [inline]
> BUG: KASAN: use-after-free in le32_to_cpuvp crypto/chacha20_generic.c:19
> [inline]
> BUG: KASAN: use-after-free in crypto_chacha20_init
> crypto/chacha20_generic.c:58 [inline]
> BUG: KASAN: use-after-free in crypto_chacha20_crypt+0xaf1/0xbd0
> crypto/chacha20_generic.c:91
> Read of size 4 at addr ffff880100000006 by task syzkaller030711/3690
>
#syz dup: general protection fault in crypto_chacha20_crypt
prev parent reply other threads:[~2017-11-29 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 15:23 KASAN: use-after-free Read in crypto_chacha20_crypt syzbot
2017-11-29 8:57 ` Eric Biggers [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=20171129085747.GA20992@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+257f413f0ea433750ffaa72b2748289380957904@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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