linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: syzbot <syzbot+e736399a2c4054612307@syzkaller.appspotmail.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	aviadye@mellanox.com, borisp@mellanox.com,
	Daniel Borkmann <daniel@iogearbox.net>,
	davejwatson@fb.com, "David S. Miller" <davem@davemloft.net>,
	David Howells <dhowells@redhat.com>,
	Eric Biggers <ebiggers3@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	john.fastabend@gmail.com, k.marinushkin@gmail.com,
	linux-crypto <linux-crypto@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Security Officers <security@kernel.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in crypto_gcm_init_common
Date: Tue, 23 Apr 2019 13:04:31 -0700	[thread overview]
Message-ID: <CAGXu5jJuU8PjPW-K=wDEaShKTenbADKwF4DcKPwNBrrynD0thg@mail.gmail.com> (raw)
In-Reply-To: <0000000000009e8ef30584976ca9@google.com>

On Thu, Mar 21, 2019 at 2:33 AM syzbot
<syzbot+e736399a2c4054612307@syzkaller.appspotmail.com> wrote:
>
> 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")

Did this regression get fixed?

-- 
Kees Cook

  reply	other threads:[~2019-04-23 20:04 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 [this message]
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='CAGXu5jJuU8PjPW-K=wDEaShKTenbADKwF4DcKPwNBrrynD0thg@mail.gmail.com' \
    --to=keescook@chromium.org \
    --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=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).