From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Carpenter Date: Tue, 08 Apr 2014 11:02:08 +0000 Subject: Re: [patch] isdnloop: several buffer overflows Message-Id: <20140408110208.GF4963@mwanda> List-Id: References: <20140408092309.GA26450@mwanda> <063D6719AE5E284EB5DD2968C1650D6D0F6F14A1@AcuExch.aculab.com> In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D0F6F14A1@AcuExch.aculab.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Laight Cc: Karsten Keil , "David S. Miller" , YOSHIFUJI Hideaki / ???? , "netdev@vger.kernel.org" , "kernel-janitors@vger.kernel.org" On Tue, Apr 08, 2014 at 09:34:09AM +0000, David Laight wrote: > From: Dan Carpenter > > There are three buffer overflows addressed in this patch. > ... > > 2) In isdnloop_parse_cmd(), p points to a 6 characters into a 60 > > character buffer so we have 54 characters. The ->eazlist[] is 11 > > characters long. I have modified the code to return if the source > > buffer is too long. > ... > > @@ -903,6 +903,8 @@ isdnloop_parse_cmd(isdnloop_card *card) > > case 7: > > /* 0x;EAZ */ > > p += 3; > > + if (strlen(p) >= sizeof(card->eazlist[0])) > > + break; > > strcpy(card->eazlist[ch - 1], p); > > break; > > case 8: > > If you've done the strlen() you might as well use memcpy(). > There are also functions that will do a bounded strlen(), > (eg memchr()). > I re-wrote the patch based on your suggestion but decided that I prefer the original just because the diff is smaller. This is a driver that no one uses and it's full of bugs. Let's not worry about optimizing the slow paths at this point. regards, dan carpenter