Michal Hocko 81be3dee96 fs/xattr.c: zero out memory copied to userspace in getxattr
getxattr uses vmalloc to allocate memory if kzalloc fails.  This is
filled by vfs_getxattr and then copied to the userspace.  vmalloc,
however, doesn't zero out the memory so if the specific implementation
of the xattr handler is sloppy we can theoretically expose a kernel
memory.  There is no real sign this is really the case but let's make
sure this will not happen and use vzalloc instead.

Fixes: 779302e67835 ("fs/xattr.c:getxattr(): improve handling of allocation failures")
Link: http://lkml.kernel.org/r/20170306103327.2766-1-mhocko@kernel.org
Acked-by: Kees Cook <keescook@chromium.org>
Reported-by: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Michal Hocko <mhocko@suse.com>
Cc: <stable@vger.kernel.org>	[3.6+]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2017-05-08 17:15:12 -07:00
..
2017-03-28 16:16:52 +02:00
2017-05-05 18:49:20 -07:00
2017-05-08 17:15:12 -07:00
2017-05-08 17:15:12 -07:00
2017-04-20 12:09:55 -06:00
2017-04-19 14:21:23 +02:00
2017-04-20 12:09:55 -06:00
2017-05-05 13:36:10 -07:00
2017-04-19 14:21:23 +02:00
2017-05-06 11:46:16 -07:00
2017-05-05 18:49:20 -07:00
2017-04-17 12:52:27 -04:00
2017-05-05 18:49:20 -07:00
2017-02-27 18:43:46 -08:00
2017-05-06 11:46:16 -07:00
2016-12-14 23:48:11 -05:00
2017-02-27 18:43:46 -08:00
2017-05-08 17:15:12 -07:00