From: Johan Hovold <johan@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4/6] USB: hub: fix non-SS hub-descriptor handling
Date: Wed, 10 May 2017 16:31:19 +0200 [thread overview]
Message-ID: <20170510143119.GH30445@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1705101009560.2061-100000@iolanthe.rowland.org>
On Wed, May 10, 2017 at 10:12:56AM -0400, Alan Stern wrote:
> On Wed, 10 May 2017, Johan Hovold wrote:
>
> > Add missing sanity check on the non-SuperSpeed hub-descriptor length in
> > order to avoid parsing and leaking two bytes of uninitialised slab data
> > through sysfs removable-attributes (or a compound-device debug
> > statement).
> >
> > Note that we only make sure that the DeviceRemovable field is always
> > present (and specifically ignore the unused PortPwrCtrlMask field) in
> > order to continue support any hubs with non-compliant descriptors. As a
> > further safeguard, the descriptor buffer is also cleared.
> >
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Cc: stable <stable@vger.kernel.org> # 2.6.12
> > Signed-off-by: Johan Hovold <johan@kernel.org>
> > ---
> > drivers/usb/core/hub.c | 13 +++++++++----
> > 1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> > index 3ff1e9f89f2d..f77a4ebde7d5 100644
> > --- a/drivers/usb/core/hub.c
> > +++ b/drivers/usb/core/hub.c
> > @@ -362,7 +362,8 @@ static void usb_set_lpm_parameters(struct usb_device *udev)
> > }
> >
> > /* USB 2.0 spec Section 11.24.4.5 */
> > -static int get_hub_descriptor(struct usb_device *hdev, void *data)
> > +static int get_hub_descriptor(struct usb_device *hdev,
> > + struct usb_hub_descriptor *desc)
> > {
> > int i, ret, size;
> > unsigned dtype;
> > @@ -378,12 +379,16 @@ static int get_hub_descriptor(struct usb_device *hdev, void *data)
> > for (i = 0; i < 3; i++) {
> > ret = usb_control_msg(hdev, usb_rcvctrlpipe(hdev, 0),
> > USB_REQ_GET_DESCRIPTOR, USB_DIR_IN | USB_RT_HUB,
> > - dtype << 8, 0, data, size,
> > + dtype << 8, 0, desc, size,
> > USB_CTRL_GET_TIMEOUT);
> > if (hub_is_superspeed(hdev)) {
> > if (ret == size)
> > return ret;
> > - } else if (ret >= (USB_DT_HUB_NONVAR_SIZE + 2)) {
> > + } else if (ret >= USB_DT_HUB_NONVAR_SIZE + 2) {
> > + /* Make sure we have the DeviceRemovable field. */
> > + size = USB_DT_HUB_NONVAR_SIZE + desc->bNbrPorts / 8 + 1;
> > + if (ret < size)
> > + return -EMSGSIZE;
>
> The logic could be simplified a little. Since we don't really care
> about the return code when an error occurs, you could just do:
>
> } else if (ret >= USB_DT_HUB_NONVAR_SIZE +
> desc->bNbrPorts / 8 + 1) {
> /* We have the entire DeviceRemovable field. */
> return ret;
> }
Sure, that would work, but I it doesn't feel right to access bNbrPorts
without first verifying we got the non-variable fields.
I considered dropping the +2 bit, but decided to keep it in the unlikely
even that there are quirky devices out there that rely on it (e.g. first
read always return 7 bytes). Spelling it out makes it sound overly
conservative though. How about I drop that instead?
Thanks,
Johan
next prev parent reply other threads:[~2017-05-10 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170510125056.29155-1-johan@kernel.org>
2017-05-10 12:50 ` [PATCH 3/6] USB: hub: fix SS hub-descriptor handling Johan Hovold
2017-05-10 14:04 ` Alan Stern
2017-05-10 14:15 ` Johan Hovold
2017-05-10 14:28 ` Alan Stern
2017-05-10 12:50 ` [PATCH 4/6] USB: hub: fix non-SS " Johan Hovold
2017-05-10 14:12 ` Alan Stern
2017-05-10 14:31 ` Johan Hovold [this message]
2017-05-10 14:41 ` Johan Hovold
2017-05-10 15:11 ` Alan Stern
2017-05-10 16:11 ` Johan Hovold
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=20170510143119.GH30445@localhost \
--to=johan@kernel.org \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.