From: Dan Aloni <dan@kernelim.com>
To: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Cc: Dan Aloni <dan@kernelim.com>, Herbert Xu <herbert@gondor.apana.org.au>
Subject: [kernel-hardening] [PATCH 1/5] crypto: fix memory leak in rsa-kcs1pad encryption
Date: Sat, 30 Dec 2017 19:58:00 +0200 [thread overview]
Message-ID: <20171230175804.7354-2-alonid@gmail.com> (raw)
In-Reply-To: <20171230175804.7354-1-alonid@gmail.com>
From: Dan Aloni <dan@kernelim.com>
The encryption mode of pkcs1pad never uses out_sg and out_buf, so
there's no need to allocate the buffer, which presently is not even
being freed.
CC: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Dan Aloni <dan@kernelim.com>
---
crypto/rsa-pkcs1pad.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/crypto/rsa-pkcs1pad.c b/crypto/rsa-pkcs1pad.c
index 2908f93c3e55..e8354084ef4e 100644
--- a/crypto/rsa-pkcs1pad.c
+++ b/crypto/rsa-pkcs1pad.c
@@ -261,15 +261,6 @@ static int pkcs1pad_encrypt(struct akcipher_request *req)
pkcs1pad_sg_set_buf(req_ctx->in_sg, req_ctx->in_buf,
ctx->key_size - 1 - req->src_len, req->src);
- req_ctx->out_buf = kmalloc(ctx->key_size, GFP_KERNEL);
- if (!req_ctx->out_buf) {
- kfree(req_ctx->in_buf);
- return -ENOMEM;
- }
-
- pkcs1pad_sg_set_buf(req_ctx->out_sg, req_ctx->out_buf,
- ctx->key_size, NULL);
-
akcipher_request_set_tfm(&req_ctx->child_req, ctx->child);
akcipher_request_set_callback(&req_ctx->child_req, req->base.flags,
pkcs1pad_encrypt_sign_complete_cb, req);
--
2.13.6
WARNING: multiple messages have this Message-ID (diff)
From: Dan Aloni <dan@kernelim.com>
To: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com
Cc: Dan Aloni <dan@kernelim.com>, Herbert Xu <herbert@gondor.apana.org.au>
Subject: [PATCH 1/5] crypto: fix memory leak in rsa-kcs1pad encryption
Date: Sat, 30 Dec 2017 19:58:00 +0200 [thread overview]
Message-ID: <20171230175804.7354-2-alonid@gmail.com> (raw)
In-Reply-To: <20171230175804.7354-1-alonid@gmail.com>
From: Dan Aloni <dan@kernelim.com>
The encryption mode of pkcs1pad never uses out_sg and out_buf, so
there's no need to allocate the buffer, which presently is not even
being freed.
CC: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Dan Aloni <dan@kernelim.com>
---
crypto/rsa-pkcs1pad.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/crypto/rsa-pkcs1pad.c b/crypto/rsa-pkcs1pad.c
index 2908f93c3e55..e8354084ef4e 100644
--- a/crypto/rsa-pkcs1pad.c
+++ b/crypto/rsa-pkcs1pad.c
@@ -261,15 +261,6 @@ static int pkcs1pad_encrypt(struct akcipher_request *req)
pkcs1pad_sg_set_buf(req_ctx->in_sg, req_ctx->in_buf,
ctx->key_size - 1 - req->src_len, req->src);
- req_ctx->out_buf = kmalloc(ctx->key_size, GFP_KERNEL);
- if (!req_ctx->out_buf) {
- kfree(req_ctx->in_buf);
- return -ENOMEM;
- }
-
- pkcs1pad_sg_set_buf(req_ctx->out_sg, req_ctx->out_buf,
- ctx->key_size, NULL);
-
akcipher_request_set_tfm(&req_ctx->child_req, ctx->child);
akcipher_request_set_callback(&req_ctx->child_req, req->base.flags,
pkcs1pad_encrypt_sign_complete_cb, req);
--
2.13.6
next prev parent reply other threads:[~2017-12-30 17:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 17:57 [kernel-hardening] [PATCH 0/5] RFC: Public key encryption of dmesg by the kernel Dan Aloni
2017-12-30 17:57 ` Dan Aloni
2017-12-30 17:58 ` Dan Aloni [this message]
2017-12-30 17:58 ` [PATCH 1/5] crypto: fix memory leak in rsa-kcs1pad encryption Dan Aloni
2017-12-30 17:58 ` [kernel-hardening] [PATCH 2/5] certs: allow in-kernel access of trusted keys Dan Aloni
2017-12-30 17:58 ` Dan Aloni
2017-12-30 18:52 ` [kernel-hardening] " Randy Dunlap
2017-12-30 18:52 ` Randy Dunlap
2017-12-30 17:58 ` [kernel-hardening] [PATCH 3/5] kernel/printk: allow kmsg to be encrypted using public key encryption Dan Aloni
2017-12-30 17:58 ` Dan Aloni
2017-12-30 20:39 ` [kernel-hardening] " Randy Dunlap
2017-12-30 20:39 ` Randy Dunlap
2017-12-30 17:58 ` [kernel-hardening] [PATCH 4/5] tools: add dmesg decryption program Dan Aloni
2017-12-30 17:58 ` Dan Aloni
2017-12-30 20:20 ` [kernel-hardening] " Randy Dunlap
2017-12-30 20:20 ` Randy Dunlap
2017-12-30 17:58 ` [kernel-hardening] [PATCH 5/5] docs: add dmesg encryption doc Dan Aloni
2017-12-30 17:58 ` Dan Aloni
2017-12-30 19:14 ` [kernel-hardening] " Boris Lukashev
2017-12-30 19:40 ` [kernel-hardening] " Randy Dunlap
2017-12-30 19:40 ` Randy Dunlap
2018-01-03 20:21 ` [kernel-hardening] " Dan Aloni
2018-01-03 20:21 ` Dan Aloni
2018-01-03 20:45 ` [kernel-hardening] " Randy Dunlap
2018-01-03 20:45 ` Randy Dunlap
2017-12-30 21:42 ` [kernel-hardening] [PATCH 0/5] RFC: Public key encryption of dmesg by the kernel Jann Horn
2018-01-03 20:41 ` Dan Aloni
2018-01-18 21:57 ` [kernel-hardening] " Pavel Machek
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=20171230175804.7354-2-alonid@gmail.com \
--to=dan@kernelim.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@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.