From: Greg KH <gregkh@linuxfoundation.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: stable@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 4.14.y] usb: hub: Guard against accesses to uninitialized BOS descriptors
Date: Fri, 20 Oct 2023 18:14:26 +0200 [thread overview]
Message-ID: <2023102016-ajar-extradite-39ac@gregkh> (raw)
In-Reply-To: <20231017060613.3580689-1-ricardo.canuelo@collabora.com>
On Tue, Oct 17, 2023 at 08:06:13AM +0200, Ricardo Cañuelo wrote:
> Many functions in drivers/usb/core/hub.c and drivers/usb/core/hub.h
> access fields inside udev->bos without checking if it was allocated and
> initialized. If usb_get_bos_descriptor() fails for whatever
> reason, udev->bos will be NULL and those accesses will result in a
> crash:
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-10-20 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 18:08 FAILED: patch "[PATCH] usb: hub: Guard against accesses to uninitialized BOS" failed to apply to 4.14-stable tree gregkh
2023-10-17 6:06 ` [PATCH 4.14.y] usb: hub: Guard against accesses to uninitialized BOS descriptors Ricardo Cañuelo
2023-10-20 16:14 ` Greg KH [this message]
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=2023102016-ajar-extradite-39ac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=ricardo.canuelo@collabora.com \
--cc=stable@vger.kernel.org \
/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