From: Greg KH <gregkh@linuxfoundation.org>
To: Kuen-Han Tsai <khtsai@google.com>
Cc: mathias.nyman@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: fix null pointer deref for xhci_urb_enqueue
Date: Fri, 17 Nov 2023 08:53:18 -0500 [thread overview]
Message-ID: <2023111705-showroom-consonant-7a7b@gregkh> (raw)
In-Reply-To: <20231117072131.2886406-1-khtsai@google.com>
On Fri, Nov 17, 2023 at 03:21:28PM +0800, Kuen-Han Tsai wrote:
> The null pointer dereference happens when xhci_free_dev() frees the
> xhci->devs[slot_id] virtual device while xhci_urb_enqueue() is
> processing a urb and checking the max packet size.
>
> [106913.850735][ T2068] usb 2-1: USB disconnect, device number 2
> [106913.856999][ T4618] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
> [106913.857488][ T4618] Call trace:
> [106913.857491][ T4618] xhci_check_maxpacket+0x30/0x2dc
> [106913.857494][ T4618] xhci_urb_enqueue+0x24c/0x47c
> [106913.857498][ T4618] usb_hcd_submit_urb+0x1f4/0xf34
> [106913.857501][ T4618] usb_submit_urb+0x4b8/0x4fc
> [106913.857503][ T4618] usb_control_msg+0x144/0x238
> [106913.857507][ T4618] do_proc_control+0x1f0/0x5bc
> [106913.857509][ T4618] usbdev_ioctl+0xdd8/0x15a8
>
> This patch adds a spinlock to the xhci_urb_enqueue function to make sure
> xhci_free_dev() and xhci_urb_enqueue() do not race and cause null
> pointer dereference.
I thought we had a lock for this already, what changed to cause this to
start triggering now, all these years later?
>
> Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
What commit id does this fix?
> ---
> drivers/usb/host/xhci.c | 38 ++++++++++++++++++++++++--------------
> 1 file changed, 24 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 884b0898d9c9..e0766ebeff0e 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -1522,23 +1522,32 @@ static int xhci_urb_enqueue(struct usb_hcd *hcd, struct urb *urb, gfp_t mem_flag
> struct urb_priv *urb_priv;
> int num_tds;
>
> - if (!urb)
> - return -EINVAL;
> - ret = xhci_check_args(hcd, urb->dev, urb->ep,
> - true, true, __func__);
> - if (ret <= 0)
> - return ret ? ret : -EINVAL;
> + spin_lock_irqsave(&xhci->lock, flags);
> +
> + if (!urb) {
> + ret = -EINVAL;
> + goto done;
> + }
Why does this have to be inside the lock? The urb can't change here,
can it?
> +
> + ret = xhci_check_args(hcd, urb->dev, urb->ep, true, true, __func__);
> + if (ret <= 0) {
> + ret = ret ? ret : -EINVAL;
> + goto done;
> + }
>
> slot_id = urb->dev->slot_id;
> ep_index = xhci_get_endpoint_index(&urb->ep->desc);
> ep_state = &xhci->devs[slot_id]->eps[ep_index].ep_state;
>
> - if (!HCD_HW_ACCESSIBLE(hcd))
> - return -ESHUTDOWN;
> + if (!HCD_HW_ACCESSIBLE(hcd)) {
> + ret = -ESHUTDOWN;
> + goto done;
Note, we now have completions, so all of this "goto done" doesn't need
to happen anymore. Not a complaint, just a suggestion for future
changes or this one, your choice.
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-17 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 7:21 Kuen-Han Tsai
2023-11-17 13:32 ` Mathias Nyman
2023-11-18 10:19 ` Kuen-Han Tsai
2023-11-20 15:33 ` Mathias Nyman
2023-11-28 13:57 ` Mathias Nyman
2023-11-28 14:01 ` [RFT PATCH 1/2] xhci: Reconfigure endpoint 0 max packet size only during endpoint reset Mathias Nyman
2023-11-28 14:01 ` [RFT PATCH 2/2] xhci: fix possible null pointer deref during xhci urb enqueue Mathias Nyman
2023-11-28 15:32 ` [RFT PATCH 1/2] xhci: Reconfigure endpoint 0 max packet size only during endpoint reset Kuen-Han Tsai
2023-11-29 14:57 ` Mathias Nyman
2023-11-28 15:01 ` [PATCH] xhci: fix null pointer deref for xhci_urb_enqueue Kuen-Han Tsai
2023-11-17 13:53 ` Greg KH [this message]
2023-11-18 11:19 ` Kuen-Han Tsai
2023-11-23 1:54 ` kernel test robot
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=2023111705-showroom-consonant-7a7b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=khtsai@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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
all inboxes | Powered by JetHome®