eCryptfs: Remove buggy and unnecessary write in file name decode routine
authorMichael Halcrow <mhalcrow@google.com>
Wed, 26 Nov 2014 17:09:16 +0000 (09:09 -0800)
committerWilly Tarreau <w@1wt.eu>
Fri, 18 Sep 2015 11:51:53 +0000 (13:51 +0200)
commitf9e6d14d33ab7e4ada2d59acaf16196626063e95
treec600e72da203d83dd0ba21bf309e84e3b6751232
parent624f4cea32b1f9897b4bf29f12d41295409b0956
eCryptfs: Remove buggy and unnecessary write in file name decode routine

commit 942080643bce061c3dd9d5718d3b745dcb39a8bc upstream.

Dmitry Chernenkov used KASAN to discover that eCryptfs writes past the
end of the allocated buffer during encrypted filename decoding. This
fix corrects the issue by getting rid of the unnecessary 0 write when
the current bit offset is 2.

Signed-off-by: Michael Halcrow <mhalcrow@google.com>
Reported-by: Dmitry Chernenkov <dmitryc@google.com>
Suggested-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
CVE-2014-9683

Signed-off-by: Willy Tarreau <w@1wt.eu>
fs/ecryptfs/crypto.c