linux-kernel - Re: [PATCH] staging: gdm724x: gdm_tty: Fix for possible null pointer dereference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150205121913.GE5336@mwanda>
Date:	Thu, 5 Feb 2015 15:19:14 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Rickard Strandqvist <rickard_strandqvist@...ctrumdigital.se>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Kiran Padwal <kiran.padwal21@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: gdm724x: gdm_tty: Fix for possible null pointer
 dereference

On Wed, Feb 04, 2015 at 06:46:34PM +0100, Rickard Strandqvist wrote:
> 2015-02-02 17:36 GMT+01:00 Sudip Mukherjee <sudipm.mukherjee@...il.com>:
> > On Thu, Jan 29, 2015 at 07:46:10PM +0100, Rickard Strandqvist wrote:
> >> diff --git a/drivers/staging/gdm724x/gdm_tty.c b/drivers/staging/gdm724x/gdm_tty.c
> >> index 001348c..66b356e 100644
> >> --- a/drivers/staging/gdm724x/gdm_tty.c
> >> +++ b/drivers/staging/gdm724x/gdm_tty.c
> >> @@ -145,7 +145,7 @@ static int gdm_tty_recv_complete(void *data,
> >>       struct gdm *gdm = tty_dev->gdm[index];
> >>
> >>       if (!GDM_TTY_READY(gdm)) {
> >> -             if (complete == RECV_PACKET_PROCESS_COMPLETE)
> >> +             if (gdm && complete == RECV_PACKET_PROCESS_COMPLETE)
> > GDM_TTY_READY() is already checking for gdm, there is no chance that gdm can be null at this point. so this additional check is not required.
> >
> > regards
> > sudip
> >>                       gdm_tty_recv(gdm, gdm_tty_recv_complete);
> >>               return TO_HOST_PORT_CLOSE;
> >>       }
> 
> Hi Sudip
> 
> Yes, GDM_TTY_READY checks gdm, but this is a if(! )
> 

You're right.  But, by that same logic, we should also test
gdm->tty_dev.  So it looks like this:

	if (!GDM_TTY_READY(gdm))  {
		if (gdm && gdm->tty_dev && complete == RECV_PACKET_PROCESS_COMPLETE)
			gdm_tty_recv(gdm, gdm_tty_recv_complete);
		return TO_HOST_PORT_CLOSE;
	}

That is really sucky...  Garbage code like this is why kernel style
doesn't favour macros.  We should just open code GDM_TTY_READY() and
gdm_tty_recv() so that people can read the code.

I wonder if "gdm->tty_dev" is the same as the "tty_dev" parameter?

regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/