KEYS: trusted: fix writing past end of buffer in trusted_read()
authorEric Biggers <ebiggers@google.com>
Thu, 2 Nov 2017 00:47:12 +0000 (00:47 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 1 Jan 2018 20:51:01 +0000 (20:51 +0000)
commitbc2acd699938b98ea7f903d67acce4a84d6b7fe8
tree30b5b71f6bf6492258264dfe3ade904abdaca65e
parent3c16f689b7430641cef4f216b0707c56184c114c
KEYS: trusted: fix writing past end of buffer in trusted_read()

commit a3c812f7cfd80cf51e8f5b7034f7418f6beb56c1 upstream.

When calling keyctl_read() on a key of type "trusted", if the
user-supplied buffer was too small, the kernel ignored the buffer length
and just wrote past the end of the buffer, potentially corrupting
userspace memory.  Fix it by instead returning the size required, as per
the documentation for keyctl_read().

We also don't even fill the buffer at all in this case, as this is
slightly easier to implement than doing a short read, and either
behavior appears to be permitted.  It also makes it match the behavior
of the "encrypted" key type.

Fixes: d00a1c72f7f4 ("keys: add new trusted key-type")
Reported-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
Reviewed-by: James Morris <james.l.morris@oracle.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
security/keys/trusted.c