summaryrefslogtreecommitdiff
path: root/fs/drop_caches.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2009-04-14 15:00:53 (GMT)
committerSteve French <sfrench@us.ibm.com>2009-04-17 01:26:50 (GMT)
commit27b87fe52baba0a55e9723030e76fce94fabcea4 (patch)
treefe1d0b6e29134e4b3160629953a37faf84c0ee17 /fs/drop_caches.c
parent88dd47fff4891545bfcfdf39146dde8380771766 (diff)
downloadlinux-fsl-qoriq-27b87fe52baba0a55e9723030e76fce94fabcea4.tar.xz
cifs: fix unicode string area word alignment in session setup
The handling of unicode string area alignment is wrong. decode_unicode_ssetup improperly assumes that it will always be preceded by a pad byte. This isn't the case if the string area is already word-aligned. This problem, combined with the bad buffer sizing for the serverDomain string can cause memory corruption. The bad alignment can make it so that the alignment of the characters is off. This can make them translate to characters that are greater than 2 bytes each. If this happens we can overflow the allocation. Fix this by fixing the alignment in CIFS_SessSetup instead so we can verify it against the head of the response. Also, clean up the workaround for improperly terminated strings by checking for a odd-length unicode buffers and then forcibly terminating them. Finally, resize the buffer for serverDomain. Now that we've fixed the alignment, it's probably fine, but a malicious server could overflow it. A better solution for handling these strings is still needed, but this should be a suitable bandaid. Signed-off-by: Jeff Layton <jlayton@redhat.com> CC: Stable <stable@vger.kernel.org> Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/drop_caches.c')
0 files changed, 0 insertions, 0 deletions