From: <gregkh@linuxfoundation.org>
To: herbert@gondor.apana.org.au, dan.carpenter@oracle.com,
gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "crypto: lrw - Free rctx->ext with kzfree" has been added to the 4.14-stable tree
Date: Thu, 05 Apr 2018 21:59:25 +0200 [thread overview]
Message-ID: <152295836514789@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
crypto: lrw - Free rctx->ext with kzfree
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
crypto-lrw-free-rctx-ext-with-kzfree.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 8c9bdab21289c211ca1ca6a5f9b7537b4a600a02 Mon Sep 17 00:00:00 2001
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 23 Mar 2018 08:14:44 +0800
Subject: crypto: lrw - Free rctx->ext with kzfree
From: Herbert Xu <herbert@gondor.apana.org.au>
commit 8c9bdab21289c211ca1ca6a5f9b7537b4a600a02 upstream.
The buffer rctx->ext contains potentially sensitive data and should
be freed with kzfree.
Cc: <stable@vger.kernel.org>
Fixes: 700cb3f5fe75 ("crypto: lrw - Convert to skcipher")
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
crypto/lrw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/crypto/lrw.c
+++ b/crypto/lrw.c
@@ -313,7 +313,7 @@ static void exit_crypt(struct skcipher_r
rctx->left = 0;
if (rctx->ext)
- kfree(rctx->ext);
+ kzfree(rctx->ext);
}
static int do_encrypt(struct skcipher_request *req, int err)
Patches currently in stable-queue which might be from herbert@gondor.apana.org.au are
queue-4.14/crypto-caam-fix-null-dereference-at-error-path.patch
queue-4.14/crypto-x86-cast5-avx-fix-ecb-encryption-when-long-sg-follows-short-one.patch
queue-4.14/crypto-arm-arm64-fix-random-regeneration-of-s_shipped.patch
queue-4.14/crypto-ccp-return-an-actual-key-size-from-rsa-max_size-callback.patch
queue-4.14/crypto-inside-secure-fix-clock-management.patch
queue-4.14/crypto-lrw-free-rctx-ext-with-kzfree.patch
queue-4.14/crypto-testmgr-fix-incorrect-values-in-pkcs-1-test-vector.patch
queue-4.14/crypto-ahash-fix-early-termination-in-hash-walk.patch
reply other threads:[~2018-04-05 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=152295836514789@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=herbert@gondor.apana.org.au \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.