diff options
| author | Jeff Layton <jlayton@redhat.com> | 2011-08-23 07:21:28 -0400 |
|---|---|---|
| committer | Steve French <sfrench@us.ibm.com> | 2011-09-19 21:14:40 -0500 |
| commit | 9438fabb73eb48055b58b89fc51e0bc4db22fabd (patch) | |
| tree | d8cb3ac7c9e9e3ead5e57b9e362bd2a7084781a4 /fs | |
| parent | 9d037a777695993ec7437e5f451647dea7919d4c (diff) | |
| download | linux-3.10-9438fabb73eb48055b58b89fc51e0bc4db22fabd.tar.gz linux-3.10-9438fabb73eb48055b58b89fc51e0bc4db22fabd.tar.bz2 linux-3.10-9438fabb73eb48055b58b89fc51e0bc4db22fabd.zip | |
cifs: fix possible memory corruption in CIFSFindNext
The name_len variable in CIFSFindNext is a signed int that gets set to
the resume_name_len in the cifs_search_info. The resume_name_len however
is unsigned and for some infolevels is populated directly from a 32 bit
value sent by the server.
If the server sends a very large value for this, then that value could
look negative when converted to a signed int. That would make that
value pass the PATH_MAX check later in CIFSFindNext. The name_len would
then be used as a length value for a memcpy. It would then be treated
as unsigned again, and the memcpy scribbles over a ton of memory.
Fix this by making the name_len an unsigned value in CIFSFindNext.
Cc: <stable@kernel.org>
Reported-by: Darren Lavender <dcl@hppine99.gbr.hp.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/cifs/cifssmb.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/cifs/cifssmb.c b/fs/cifs/cifssmb.c index aac37d99a48..a80f7bd97b9 100644 --- a/fs/cifs/cifssmb.c +++ b/fs/cifs/cifssmb.c @@ -4079,7 +4079,8 @@ int CIFSFindNext(const int xid, struct cifs_tcon *tcon, T2_FNEXT_RSP_PARMS *parms; char *response_data; int rc = 0; - int bytes_returned, name_len; + int bytes_returned; + unsigned int name_len; __u16 params, byte_count; cFYI(1, "In FindNext"); |