From: Herbert Xu <herbert@gondor.apana.org.au>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: crypto: use-after-free in hash_sock_destruct_common
Date: Wed, 13 Jan 2016 14:57:29 +0800 [thread overview]
Message-ID: <20160113065729.GA8123@gondor.apana.org.au> (raw)
In-Reply-To: <CACT4Y+YP0Ppj41P9mX1SPSEXkV=ffe0vuK1Ap7r0Ub8GROD5nQ@mail.gmail.com>
On Tue, Jan 12, 2016 at 07:31:03PM +0100, Dmitry Vyukov wrote:
>
> The following program triggers use-after-free in
> hash_sock_destruct_common. This is on master of
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
> (cd7e98414462b9db70067ac29896c58210b13b69). I've also seen a similar
> crash in skcipher_sock_destruct_common.
OK the new compatibility nokey path introduced some new problems.
Please try the following patches.
Thanks,
--
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
next prev parent reply other threads:[~2016-01-13 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:31 Dmitry Vyukov
2016-01-13 6:57 ` Herbert Xu [this message]
2016-01-13 6:59 ` crypto: af_alg - Allow af_af_alg_release_parent to be called on nokey path Herbert Xu
2016-01-13 7:00 ` [PATCH 2/4] crypto: algif_hash - Remove custom release parent function Herbert Xu
2016-01-13 7:01 ` [PATCH 3/4] crypto: algif_skcipher " Herbert Xu
2016-01-13 7:03 ` [PATCH 4/4] crypto: af_alg - Forbid bind(2) when nokey child sockets are present Herbert Xu
[not found] ` <CACT4Y+YOiaC1px6SD2hTAGwSd4i8GsTm59uQ+ux1U8EzdoQfPA@mail.gmail.com>
2016-01-13 10:27 ` crypto: use-after-free in hash_sock_destruct_common Dmitry Vyukov
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=20160113065729.GA8123@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@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
all inboxes | Powered by JetHome®