From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+fa2ed481fed0c7ace1571b88a89dfd49ffd89cb6@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: general protection fault in crypto_chacha20_crypt
Date: Mon, 11 Dec 2017 11:06:09 -0800 [thread overview]
Message-ID: <20171211190609.GC62691@gmail.com> (raw)
In-Reply-To: <20171129092438.GC20992@zzz.localdomain>
On Wed, Nov 29, 2017 at 01:24:38AM -0800, Eric Biggers wrote:
>
> The bug is that the skcipher_walk API doesn't set the IV for zero-length inputs,
> while some algorithms (e.g. ChaCha20) access the IV even if the input is
> zero-length. So it was dereferencing a pointer which came from uninitialized
> stack memory. I've sent out a fix:
>
> "crypto: skcipher - set walk.iv for zero-length inputs"
>
#syz fix: crypto: skcipher - set walk.iv for zero-length inputs
prev parent reply other threads:[~2017-12-11 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 14:22 general protection fault in crypto_chacha20_crypt syzbot
2017-11-29 9:24 ` Eric Biggers
2017-12-11 19:06 ` 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=20171211190609.GC62691@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+fa2ed481fed0c7ace1571b88a89dfd49ffd89cb6@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;
as well as URLs for NNTP newsgroup(s).