linux/fs/crypto
Eric Biggers b2ac5d4516 fscrypt: fix dereference of NULL user_key_payload
commit d60b5b7854 upstream.

When an fscrypt-encrypted file is opened, we request the file's master
key from the keyrings service as a logon key, then access its payload.
However, a revoked key has a NULL payload, and we failed to check for
this.  request_key() *does* skip revoked keys, but there is still a
window where the key can be revoked before we acquire its semaphore.

Fix it by checking for a NULL payload, treating it like a key which was
already revoked at the time it was requested.

Fixes: 88bd6ccdcd ("ext4 crypto: add encryption key management facilities")
Reviewed-by: James Morris <james.l.morris@oracle.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
History 2017-10-27 10:38:10 +02:00
..
crypto.c fscrypt: remove broken support for detecting keyring key revocation 2017-03-31 10:31:46 +02:00
fname.c fscrypt: avoid collisions when presenting long encrypted filenames 2017-05-25 15:44:38 +02:00
Kconfig fs crypto: move per-file encryption from f2fs tree to fs/crypto 2016-03-17 21:19:33 -07:00
keyinfo.c fscrypt: fix dereference of NULL user_key_payload 2017-10-27 10:38:10 +02:00
Makefile fs crypto: move per-file encryption from f2fs tree to fs/crypto 2016-03-17 21:19:33 -07:00
policy.c fscrypt: fix context consistency check when key(s) unavailable 2017-05-20 14:28:41 +02:00