From: Greg KH <gregkh@linuxfoundation.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
linux@roeck-us.net, kernel@collabora.com
Subject: Re: [PATCH] usb: hub: Guard against accesses to uninitialized BOS descriptors
Date: Wed, 30 Aug 2023 12:13:44 +0200 [thread overview]
Message-ID: <2023083007-vowed-latitude-acef@gregkh> (raw)
In-Reply-To: <20230830100418.1952143-1-ricardo.canuelo@collabora.com>
On Wed, Aug 30, 2023 at 12:04:18PM +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:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000018
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 5 PID: 17818 Comm: kworker/5:1 Tainted: G W 5.15.108-18910-gab0e1cb584e1 #1 <HASH:1f9e 1>
> Hardware name: Google Kindred/Kindred, BIOS Google_Kindred.12672.413.0 02/03/2021
> Workqueue: usb_hub_wq hub_event
> RIP: 0010:hub_port_reset+0x193/0x788
> Code: 89 f7 e8 20 f7 15 00 48 8b 43 08 80 b8 96 03 00 00 03 75 36 0f b7 88 92 03 00 00 81 f9 10 03 00 00 72 27 48 8b 80 a8 03 00 00 <48> 83 78 18 00 74 19 48 89 df 48 8b 75 b0 ba 02 00 00 00 4c 89 e9
> RSP: 0018:ffffab740c53fcf8 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffffa1bc5f678000 RCX: 0000000000000310
> RDX: fffffffffffffdff RSI: 0000000000000286 RDI: ffffa1be9655b840
> RBP: ffffab740c53fd70 R08: 00001b7d5edaa20c R09: ffffffffb005e060
> R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
> R13: ffffab740c53fd3e R14: 0000000000000032 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffffa1be96540000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000018 CR3: 000000022e80c005 CR4: 00000000003706e0
> Call Trace:
> hub_event+0x73f/0x156e
> ? hub_activate+0x5b7/0x68f
> process_one_work+0x1a2/0x487
> worker_thread+0x11a/0x288
> kthread+0x13a/0x152
> ? process_one_work+0x487/0x487
> ? kthread_associate_blkcg+0x70/0x70
> ret_from_fork+0x1f/0x30
Did you mean to loose the indentation here?
> Fall back to a default behavior if the BOS descriptor isn't accessible
> and skip all the functionalities that depend on it: LPM support checks,
> Super Speed capabilitiy checks, U1/U2 states setup.
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> Cc: stable <stable@vger.kernel.org>
What commit id does this fix?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-30 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 10:04 [PATCH] usb: hub: Guard against accesses to uninitialized BOS descriptors Ricardo Cañuelo
2023-08-30 10:13 ` Greg KH [this message]
2023-08-30 10:56 ` Ricardo Cañuelo
2023-08-30 11:01 ` Ricardo Cañuelo
2023-08-30 11:12 ` Greg KH
2023-09-22 5:40 ` Ricardo Cañuelo
2023-09-22 9:12 ` Greg KH
2023-09-22 9:38 ` Ricardo Cañuelo
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=2023083007-vowed-latitude-acef@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ricardo.canuelo@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox