From: Quentin Casasnovas <quentin.casasnovas@oracle.com>
To: Adam Lee <adam8157@gmail.com>
Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
Phil Turnbull <phil.turnbull@oracle.com>,
Oliver Neukum <oneukum@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] cdc-acm: prevent infinite loop when parsing CDC headers.
Date: Mon, 13 Apr 2015 18:02:27 +0200 [thread overview]
Message-ID: <20150413160227.GF12442@chrystal.uk.oracle.com> (raw)
In-Reply-To: <20150413154827.GA2458@adam-laptop>
On Mon, Apr 13, 2015 at 11:48:27PM +0800, Adam Lee wrote:
> On Mon, Apr 13, 2015 at 05:24:04PM +0200, Quentin Casasnovas wrote:
> > Phil and I found out a problem with commit:
> >
> > 7e860a6e ("cdc-acm: add sanity checks")
> >
> > It added some sanity checks to ignore potential garbage in CDC headers but
> > also introduced a potential infinite loop. This can happen at the first
> > loop iteration (elength = 0 in that case) if the description isn't a
> > DT_CS_INTERFACE or later if 'buffer[0]' is zero.
> >
> > It should also be noted that the wrong length was being added to 'buffer'
> > in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength was
> > assigned after that check in the loop.
> >
> > A specially crafted USB device could be used to trigger this infinite loop.
>
> Yes, "elength = buffer[0]" should be moved to the front of
> USB_DT_CS_INTERFACE check, ACK this part.
>
> But I don't know in what case the buffer[0] could be zero, if it
> happens, better to set elength 1 then goto next_desc? (I'm not a
> maintainer, pleas also consider others' opinion)
>
Hi Adam,
I'm happy to change it as you suggest, though at that point we'll probably
be trying to parse garbage anyway.
If nobody had a different opinion in the meantime, I'll send a v2 tomorrow.
Thanks for the review :)
Quentin
next prev parent reply other threads:[~2015-04-13 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 15:24 [PATCH] cdc-acm: prevent infinite loop when parsing CDC headers Quentin Casasnovas
2015-04-13 15:48 ` Adam Lee
2015-04-13 16:02 ` Quentin Casasnovas [this message]
2015-04-13 15:53 ` Quentin Casasnovas
2015-04-13 16:20 ` Sergei Shtylyov
2015-04-14 11:01 ` Sergei Shtylyov
2015-04-14 9:25 ` [PATCH v2] " Quentin Casasnovas
2015-04-20 11:54 ` Quentin Casasnovas
2015-04-20 14:27 ` Greg Kroah-Hartman
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=20150413160227.GF12442@chrystal.uk.oracle.com \
--to=quentin.casasnovas@oracle.com \
--cc=adam8157@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=phil.turnbull@oracle.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