aboutsummaryrefslogtreecommitdiffstats
path: root/fs/binfmt_elf_fdpic.c
diff options
context:
space:
mode:
authorDan Rosenberg <drosenberg@vsecurity.com>2011-02-14 16:04:23 -0500
committerChris Mason <chris.mason@oracle.com>2011-02-14 16:04:23 -0500
commit51788b1bdd0d68345bab0af4301e7fa429277228 (patch)
tree52895ef3c348c2dfa1f1ef2c4557d9f7515dfc3b /fs/binfmt_elf_fdpic.c
parent6848ad6461e551849ba3c32d945d4f45e96453a6 (diff)
downloadkernel_samsung_tuna-51788b1bdd0d68345bab0af4301e7fa429277228.zip
kernel_samsung_tuna-51788b1bdd0d68345bab0af4301e7fa429277228.tar.gz
kernel_samsung_tuna-51788b1bdd0d68345bab0af4301e7fa429277228.tar.bz2
btrfs: prevent heap corruption in btrfs_ioctl_space_info()
Commit bf5fc093c5b625e4259203f1cee7ca73488a5620 refactored btrfs_ioctl_space_info() and introduced several security issues. space_args.space_slots is an unsigned 64-bit type controlled by a possibly unprivileged caller. The comparison as a signed int type allows providing values that are treated as negative and cause the subsequent allocation size calculation to wrap, or be truncated to 0. By providing a size that's truncated to 0, kmalloc() will return ZERO_SIZE_PTR. It's also possible to provide a value smaller than the slot count. The subsequent loop ignores the allocation size when copying data in, resulting in a heap overflow or write to ZERO_SIZE_PTR. The fix changes the slot count type and comparison typecast to u64, which prevents truncation or signedness errors, and also ensures that we don't copy more data than we've allocated in the subsequent loop. Note that zero-size allocations are no longer possible since there is already an explicit check for space_args.space_slots being 0 and truncation of this value is no longer an issue. Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com> Signed-off-by: Josef Bacik <josef@redhat.com> Reviewed-by: Josef Bacik <josef@redhat.com> Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/binfmt_elf_fdpic.c')
0 files changed, 0 insertions, 0 deletions