From: Herbert Xu <herbert@gondor.apana.org.au>
To: syzbot <syzbot+afb77bdbaca0cda9e991@syzkaller.appspotmail.com>
Cc: ardb@kernel.org, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, t-kristo@ti.com
Subject: Re: WARNING: refcount bug in crypto_mod_get
Date: Fri, 5 Jun 2020 22:38:18 +1000 [thread overview]
Message-ID: <20200605123818.GA3984@gondor.apana.org.au> (raw)
In-Reply-To: <00000000000004f67705a4992160@google.com>
On Fri, May 01, 2020 at 10:01:14AM -0700, syzbot wrote:
>
> ------------[ cut here ]------------
> refcount_t: addition on 0; use-after-free.
...
> refcount_add include/linux/refcount.h:204 [inline]
> refcount_inc include/linux/refcount.h:241 [inline]
> crypto_alg_get crypto/internal.h:87 [inline]
> crypto_mod_get+0xc6/0xf0 crypto/api.c:37
> crypto_spawn_alg.isra.0+0xa8/0x110 crypto/algapi.c:723
> crypto_spawn_tfm2+0x19/0xb0 crypto/algapi.c:763
> crypto_spawn_aead include/crypto/internal/aead.h:102 [inline]
> pcrypt_aead_init_tfm+0x144/0x273 crypto/pcrypt.c:182
> crypto_aead_init_tfm+0x138/0x1a0 crypto/aead.c:140
> crypto_create_tfm+0xd5/0x2f0 crypto/api.c:454
> crypto_alloc_tfm+0x100/0x340 crypto/api.c:526
> aead_bind+0x69/0x170 crypto/algif_aead.c:483
> alg_bind+0x260/0x530 crypto/af_alg.c:182
> __sys_bind+0x20e/0x250 net/socket.c:1662
> __do_sys_bind net/socket.c:1673 [inline]
> __se_sys_bind net/socket.c:1671 [inline]
> __x64_sys_bind+0x6f/0xb0 net/socket.c:1671
> do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:295
> entry_SYSCALL_64_after_hwframe+0x49/0xb3
This should be fixed already:
#syz fix: crypto: api - Fix use-after-free and race in crypto_spawn_alg
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2020-06-05 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:01 syzbot
2020-06-05 12:38 ` Herbert Xu [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=20200605123818.GA3984@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+afb77bdbaca0cda9e991@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=t-kristo@ti.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
all inboxes | Powered by JetHome®