All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Eric Biggers <ebiggers3@gmail.com>, keyrings@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
	Andy Lutomirski <luto@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Eric Biggers <ebiggers@google.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] KEYS: encrypted: avoid encrypting/decrypting stack buffers
Date: Sat, 01 Apr 2017 22:23:57 -0400	[thread overview]
Message-ID: <1491099837.3499.163.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170401191709.25170-1-ebiggers3@gmail.com>

Hi Eric,

On Sat, 2017-04-01 at 12:17 -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Since v4.9, the crypto API cannot (normally) be used to encrypt/decrypt
> stack buffers because the stack may be virtually mapped.  Fix this for
> the padding buffers in encrypted-keys by using ZERO_PAGE for the
> encryption padding and by allocating a temporary heap buffer for the
> decryption padding.
> 
> Tested with CONFIG_DEBUG_SG=y:
> 	keyctl new_session
> 	keyctl add user master "abcdefghijklmnop" @s
> 	keyid=$(keyctl add encrypted desc "new user:master 25" @s)
> 	datablob="$(keyctl pipe $keyid)"
> 	keyctl unlink $keyid
> 	keyid=$(keyctl add encrypted desc "load $datablob" @s)
> 	datablob2="$(keyctl pipe $keyid)"
> 	[ "$datablob" = "$datablob2" ] && echo "Success!"

Have you created an encrypted key on a kernel without this patch and
attempted to load that key on a kernel with this patch?  Does it still
work?

Mimi

> 
> Cc: Andy Lutomirski <luto@kernel.org>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org # 4.9+
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  security/keys/encrypted-keys/encrypted.c | 17 +++++++++--------
>  1 file changed, 9 insertions(+), 8 deletions(-)
> 
> diff --git a/security/keys/encrypted-keys/encrypted.c b/security/keys/encrypted-keys/encrypted.c
> index 0010955d7876..1845d47474a0 100644
> --- a/security/keys/encrypted-keys/encrypted.c
> +++ b/security/keys/encrypted-keys/encrypted.c
> @@ -480,12 +480,9 @@ static int derived_key_encrypt(struct encrypted_key_payload *epayload,
>  	struct skcipher_request *req;
>  	unsigned int encrypted_datalen;
>  	u8 iv[AES_BLOCK_SIZE];
> -	unsigned int padlen;
> -	char pad[16];
>  	int ret;
> 
>  	encrypted_datalen = roundup(epayload->decrypted_datalen, blksize);
> -	padlen = encrypted_datalen - epayload->decrypted_datalen;
> 
>  	req = init_skcipher_req(derived_key, derived_keylen);
>  	ret = PTR_ERR(req);
> @@ -493,11 +490,10 @@ static int derived_key_encrypt(struct encrypted_key_payload *epayload,
>  		goto out;
>  	dump_decrypted_data(epayload);
> 
> -	memset(pad, 0, sizeof pad);
>  	sg_init_table(sg_in, 2);
>  	sg_set_buf(&sg_in[0], epayload->decrypted_data,
>  		   epayload->decrypted_datalen);
> -	sg_set_buf(&sg_in[1], pad, padlen);
> +	sg_set_page(&sg_in[1], ZERO_PAGE(0), AES_BLOCK_SIZE, 0);
> 
>  	sg_init_table(sg_out, 1);
>  	sg_set_buf(sg_out, epayload->encrypted_data, encrypted_datalen);
> @@ -584,9 +580,14 @@ static int derived_key_decrypt(struct encrypted_key_payload *epayload,
>  	struct skcipher_request *req;
>  	unsigned int encrypted_datalen;
>  	u8 iv[AES_BLOCK_SIZE];
> -	char pad[16];
> +	u8 *pad;
>  	int ret;
> 
> +	/* Throwaway buffer to hold the unused zero padding at the end */
> +	pad = kmalloc(AES_BLOCK_SIZE, GFP_KERNEL);
> +	if (!pad)
> +		return -ENOMEM;
> +
>  	encrypted_datalen = roundup(epayload->decrypted_datalen, blksize);
>  	req = init_skcipher_req(derived_key, derived_keylen);
>  	ret = PTR_ERR(req);
> @@ -594,13 +595,12 @@ static int derived_key_decrypt(struct encrypted_key_payload *epayload,
>  		goto out;
>  	dump_encrypted_data(epayload, encrypted_datalen);
> 
> -	memset(pad, 0, sizeof pad);
>  	sg_init_table(sg_in, 1);
>  	sg_init_table(sg_out, 2);
>  	sg_set_buf(sg_in, epayload->encrypted_data, encrypted_datalen);
>  	sg_set_buf(&sg_out[0], epayload->decrypted_data,
>  		   epayload->decrypted_datalen);
> -	sg_set_buf(&sg_out[1], pad, sizeof pad);
> +	sg_set_buf(&sg_out[1], pad, AES_BLOCK_SIZE);
> 
>  	memcpy(iv, epayload->iv, sizeof(iv));
>  	skcipher_request_set_crypt(req, sg_in, sg_out, encrypted_datalen, iv);
> @@ -612,6 +612,7 @@ static int derived_key_decrypt(struct encrypted_key_payload *epayload,
>  		goto out;
>  	dump_decrypted_data(epayload);
>  out:
> +	kfree(pad);
>  	return ret;
>  }
> 

  reply	other threads:[~2017-04-02  2:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 19:17 [PATCH] KEYS: encrypted: avoid encrypting/decrypting stack buffers Eric Biggers
2017-04-02  2:23 ` Mimi Zohar [this message]
2017-04-02  3:33   ` Eric Biggers
2017-04-02  3:33     ` Eric Biggers
2017-04-03 15:55     ` Mimi Zohar
2017-04-03 18:21       ` Eric Biggers
2017-04-03 18:21         ` Eric Biggers
2017-04-03 15:44 ` David Howells

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=1491099837.3499.163.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@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.