From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+6fbc13c3b1ed2105e7a2e516be43d6a0624a59c0@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 aead_recvmsg
Date: Fri, 1 Dec 2017 11:11:08 -0800 [thread overview]
Message-ID: <20171201191108.GC142348@gmail.com> (raw)
In-Reply-To: <001a113ebb5ece8a7a055efb7676@google.com>
On Mon, Nov 27, 2017 at 10:56:46AM -0800, syzbot wrote:
> ==================================================================
> BUG: KASAN: use-after-free in skcipher_request_set_tfm
> include/crypto/skcipher.h:499 [inline]
> BUG: KASAN: use-after-free in crypto_aead_copy_sgl
> crypto/algif_aead.c:85 [inline]
> BUG: KASAN: use-after-free in _aead_recvmsg crypto/algif_aead.c:210 [inline]
> BUG: KASAN: use-after-free in aead_recvmsg+0x1552/0x1970
> crypto/algif_aead.c:313
> Read of size 4 at addr ffff8801c7194e5c by task syzkaller438416/3340
>
> CPU: 0 PID: 3340 Comm: syzkaller438416 Not tainted 4.14.0-next-20171124+ #51
> Hardware name: Google Google Compute Engine/Google Compute Engine,
> BIOS Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> print_address_description+0x73/0x250 mm/kasan/report.c:252
> kasan_report_error mm/kasan/report.c:351 [inline]
> kasan_report+0x25b/0x340 mm/kasan/report.c:409
> __asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:429
> skcipher_request_set_tfm include/crypto/skcipher.h:499 [inline]
> crypto_aead_copy_sgl crypto/algif_aead.c:85 [inline]
> _aead_recvmsg crypto/algif_aead.c:210 [inline]
> aead_recvmsg+0x1552/0x1970 crypto/algif_aead.c:313
> sock_recvmsg_nosec net/socket.c:805 [inline]
> sock_recvmsg+0xc9/0x110 net/socket.c:812
> ___sys_recvmsg+0x29b/0x630 net/socket.c:2207
> __sys_recvmsg+0xe2/0x210 net/socket.c:2252
> SYSC_recvmsg net/socket.c:2264 [inline]
> SyS_recvmsg+0x2d/0x50 net/socket.c:2259
> entry_SYSCALL_64_fastpath+0x1f/0x96
#syz fix: crypto: algif_aead - fix reference counting of null skcipher
prev parent reply other threads:[~2017-12-01 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 18:56 KASAN: use-after-free Read in aead_recvmsg syzbot
2017-11-27 22:02 ` Stephan Müller
2017-11-27 22:43 ` Eric Biggers
2017-11-28 6:30 ` Stephan Mueller
2017-11-28 7:29 ` Eric Biggers
2017-11-28 7:43 ` Stephan Mueller
2017-11-29 5:23 ` Herbert Xu
2017-12-01 19:11 ` 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=20171201191108.GC142348@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+6fbc13c3b1ed2105e7a2e516be43d6a0624a59c0@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