aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2016-02-05 19:37:27 -0800
committerMister Oyster <oysterized@gmail.com>2017-04-13 12:33:01 +0200
commite865647cbdbdc63e684aebc1a8441ffaa81330b9 (patch)
tree46b8c58c9eb9ae26210d496b0d46319cc8b9b5c2
parent28c47722bccafb2d343dd1d970a05413ed633041 (diff)
f2fs crypto: check for too-short encrypted file names
This patch adopts: ext4 crypto: check for too-short encrypted file names An encrypted file name should never be shorter than an 16 bytes, the AES block size. The 3.10 crypto layer will oops and crash the kernel if ciphertext shorter than the block size is passed to it. Fortunately, in modern kernels the crypto layer will not crash the kernel in this scenario, but nevertheless, it represents a corrupted directory, and we should detect it and mark the file system as corrupted so that e2fsck can fix this. Signed-off-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
-rw-r--r--fs/f2fs/crypto_fname.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/fs/f2fs/crypto_fname.c b/fs/f2fs/crypto_fname.c
index e7aa67c37..905c06535 100644
--- a/fs/f2fs/crypto_fname.c
+++ b/fs/f2fs/crypto_fname.c
@@ -317,7 +317,10 @@ int f2fs_fname_disk_to_usr(struct inode *inode,
oname->len = iname->len;
return oname->len;
}
-
+ if (iname->len < F2FS_CRYPTO_BLOCK_SIZE) {
+ printk("encrypted inode too small");
+ return -EUCLEAN;
+ }
if (F2FS_I(inode)->i_crypt_info)
return f2fs_fname_decrypt(inode, iname, oname);