aboutsummaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorBenjamin Randazzo <benjamin@randazzo.fr>2015-07-25 16:36:50 +0200
committerSimon Shields <keepcalm444@gmail.com>2016-03-15 18:30:55 +1100
commit18bac65c1273d0e059f9174c4e8e9c7e45a12911 (patch)
tree8a0af48a85de66ec6968d3c9560718522e937fe7 /security
parent60d05551c60819bea1c8cfe1e5427a47a21bccd1 (diff)
downloadkernel_samsung_smdk4412-18bac65c1273d0e059f9174c4e8e9c7e45a12911.zip
kernel_samsung_smdk4412-18bac65c1273d0e059f9174c4e8e9c7e45a12911.tar.gz
kernel_samsung_smdk4412-18bac65c1273d0e059f9174c4e8e9c7e45a12911.tar.bz2
md: use kzalloc() when bitmap is disabled
commit b6878d9e03043695dbf3fa1caa6dfc09db225b16 upstream. In drivers/md/md.c get_bitmap_file() uses kmalloc() for creating a mdu_bitmap_file_t called "file". 5769 file = kmalloc(sizeof(*file), GFP_NOIO); 5770 if (!file) 5771 return -ENOMEM; This structure is copied to user space at the end of the function. 5786 if (err == 0 && 5787 copy_to_user(arg, file, sizeof(*file))) 5788 err = -EFAULT But if bitmap is disabled only the first byte of "file" is initialized with zero, so it's possible to read some bytes (up to 4095) of kernel space memory from user space. This is an information leak. 5775 /* bitmap disabled, zero the first byte and copy out */ 5776 if (!mddev->bitmap_info.file) 5777 file->pathname[0] = '\0'; Change-Id: I7cd2a3c7fad2e2cb9edb8b4eff2af8a3a8f40149 Signed-off-by: Benjamin Randazzo <benjamin@randazzo.fr> Signed-off-by: NeilBrown <neilb@suse.com> [lizf: Backported to 3.4: fix both branches] Signed-off-by: Zefan Li <lizefan@huawei.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions