linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	Shyam Prasad N <nspmangalore@gmail.com>
Subject: Re: [PATCH][CIFS] Fix uninitialized pointer access to dacl_ptr in build_sec_desc
Date: Wed, 23 Jun 2021 09:17:49 -0500	[thread overview]
Message-ID: <CAH2r5msXgL5PZB8k99MJW-u5bNbHY9QxS8hKUasRqYTYR-z0bQ@mail.gmail.com> (raw)
In-Reply-To: <87bl7wreou.fsf@suse.com>

On Wed, Jun 23, 2021 at 6:41 AM Aurélien Aptel <aaptel@suse.com> wrote:
>
> Steve French <smfrench@gmail.com> writes:
>
> >     smb3: fix possible access to uninitialized pointer to DACL
> >
> >     dacl_ptr can be null so we must check for it (ie if dacloffset is
> > set) everywhere dacl_ptr is
> >     used in build_sec_desc - and we were missing one check
> >
> >     Addresses-Coverity: 1475598 ("Explicit null dereference")
>
> Looks OK since dacl_ptr is only set if dacloffset is set but it would
> be clearer if you check for dacl_ptr directly no? Any reason you are
> checking this way?
>
> I think this is clearer, unless I'm missing something:
>
> ndacl_ptr->num_aces = dacl_ptr ? dacl_ptr->num_aces : 0;

I agree that your suggestion is clearer but I was trying to match the
existing checks in the same code.
Will change both to your suggestion which is clearer.


> >
> >
> > --
> > Thanks,
> >
> > Steve
> > From ec06cb04376e5abc927a9b85dd768ce8728965bb Mon Sep 17 00:00:00 2001
> > From: Steve French <stfrench@microsoft.com>
> > Date: Tue, 22 Jun 2021 17:54:50 -0500
> > Subject: [PATCH] smb3: fix possible access to uninitialized pointer to DACL
> >
> > dacl_ptr can be null so we must check for it everywhere it is
> > used in build_sec_desc.
> >
> > Addresses-Coverity: 1475598 ("Explicit null dereference")
> > Signed-off-by: Steve French <stfrench@microsoft.com>
> > ---
> >  fs/cifs/cifsacl.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/cifs/cifsacl.c b/fs/cifs/cifsacl.c
> > index 784407f9280f..25a8139336fa 100644
> > --- a/fs/cifs/cifsacl.c
> > +++ b/fs/cifs/cifsacl.c
> > @@ -1308,7 +1308,7 @@ static int build_sec_desc(struct cifs_ntsd *pntsd, struct cifs_ntsd *pnntsd,
> >               ndacl_ptr = (struct cifs_acl *)((char *)pnntsd + ndacloffset);
> >               ndacl_ptr->revision =
> >                       dacloffset ? dacl_ptr->revision : cpu_to_le16(ACL_REVISION);
> > -             ndacl_ptr->num_aces = dacl_ptr->num_aces;
> > +             ndacl_ptr->num_aces = dacloffset ? dacl_ptr->num_aces : 0;
> >
> >               if (uid_valid(uid)) { /* chown */
> >                       uid_t id;
> > --
> > 2.30.2
> >
>
> --
> Aurélien Aptel / SUSE Labs Samba Team
> GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
> SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
> GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
>


-- 
Thanks,

Steve

  reply	other threads:[~2021-06-23 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 23:02 [PATCH][CIFS] Fix uninitialized pointer access to dacl_ptr in build_sec_desc Steve French
2021-06-23 11:41 ` Aurélien Aptel
2021-06-23 14:17   ` Steve French [this message]
2021-06-24  0:27     ` Steve French

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=CAH2r5msXgL5PZB8k99MJW-u5bNbHY9QxS8hKUasRqYTYR-z0bQ@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=aaptel@suse.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@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;
as well as URLs for NNTP newsgroup(s).