From: Jeff Layton <jlayton@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org, k.skarlatos@gmail.com,
shirishpargaonkar@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: fix bad buffer length check in coalesce_t2
Date: Mon, 2 Jan 2012 06:09:01 -0500 [thread overview]
Message-ID: <20120102060901.0853a6bd@tlielax.poochiereds.net> (raw)
In-Reply-To: <CAH2r5msQU=_2X799oGt1MeuejSQX2HLLW4-FgnXqg6DXHwTTZA@mail.gmail.com>
On Sun, 1 Jan 2012 17:35:18 -0600
Steve French <smfrench@gmail.com> wrote:
> Any easy repro?
Not for me. It seems to depend on a variety of factors including the
infolevel used, the length of the filenames, and possibly their order
in the response.
> On Jan 1, 2012 9:34 AM, "Jeff Layton" <jlayton@redhat.com> wrote:
>
> > The current check looks to see if the RFC1002 length is larger than
> > CIFSMaxBufSize, and fails if it is. The buffer is actually larger than
> > that by MAX_CIFS_HDR_SIZE.
> >
> > This bug has been around for a long time, but the fact that we used to
> > cap the clients MaxBufferSize at the same level as the server tended
> > to paper over it. Commit c974befa changed that however and caused this
> > bug to bite in more cases.
> >
> > Reported-and-Tested-by: Konstantinos Skarlatos <k.skarlatos@gmail.com>
> > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > ---
> > fs/cifs/connect.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> > index 8cd4b52..27c4f25 100644
> > --- a/fs/cifs/connect.c
> > +++ b/fs/cifs/connect.c
> > @@ -282,7 +282,7 @@ static int coalesce_t2(struct smb_hdr *psecond, struct
> > smb_hdr *pTargetSMB)
> > byte_count = be32_to_cpu(pTargetSMB->smb_buf_length);
> > byte_count += total_in_buf2;
> > /* don't allow buffer to overflow */
> > - if (byte_count > CIFSMaxBufSize)
> > + if (byte_count > CIFSMaxBufSize + MAX_CIFS_HDR_SIZE - 4)
> > return -ENOBUFS;
> > pTargetSMB->smb_buf_length = cpu_to_be32(byte_count);
> >
> > --
> > 1.7.7.4
> >
> >
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-01-02 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 15:34 Jeff Layton
[not found] ` <CAH2r5msQU=_2X799oGt1MeuejSQX2HLLW4-FgnXqg6DXHwTTZA@mail.gmail.com>
2012-01-02 11:09 ` Jeff Layton [this message]
2012-01-03 16:22 ` Shirish Pargaonkar
2012-01-03 22:46 ` Shirish Pargaonkar
2012-01-04 14:09 ` Jeff Layton
2012-01-04 15:08 ` Shirish Pargaonkar
2012-01-04 16:14 ` Steve French
2012-01-04 16:29 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120102060901.0853a6bd@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=k.skarlatos@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shirishpargaonkar@gmail.com \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®