From: Greg KH <gregkh@linuxfoundation.org>
To: Mazin Al Haddad <mazinalhaddad05@gmail.com>
Cc: pontus.fuchs@gmail.com, netdev@vger.kernel.org, kvalo@kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+1bc2c2afd44f820a669f@syzkaller.appspotmail.com,
edumazet@google.com, paskripkin@gmail.com, kuba@kernel.org,
pabeni@redhat.com,
linux-kernel-mentees@lists.linuxfoundation.org,
davem@davemloft.net
Subject: Re: [PATCH] ar5523: check endpoints type and direction in probe()
Date: Wed, 24 Aug 2022 08:04:35 +0200 [thread overview]
Message-ID: <YwW/cw2cXLEd5xFo@kroah.com> (raw)
In-Reply-To: <20220823222436.514204-1-mazinalhaddad05@gmail.com>
On Wed, Aug 24, 2022 at 01:24:38AM +0300, Mazin Al Haddad wrote:
> Fixes a bug reported by syzbot, where a warning occurs in usb_submit_urb()
> due to the wrong endpoint type. There is no check for both the number
> of endpoints and the type which causes an error as the code tries to
> send a URB to the wrong endpoint.
>
> Fix it by adding a check for the number of endpoints and the
> direction/type of the endpoints. If the endpoints do not match the
> expected configuration -ENODEV is returned.
>
> Syzkaller report:
>
> usb 1-1: BOGUS urb xfer, pipe 3 != type 1
> WARNING: CPU: 1 PID: 71 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502
> Modules linked in:
> CPU: 1 PID: 71 Comm: kworker/1:2 Not tainted 5.19.0-rc7-syzkaller-00150-g32f02a211b0a #0
> Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022
> Workqueue: usb_hub_wq hub_event
> Call Trace:
> <TASK>
> ar5523_cmd+0x420/0x790 drivers/net/wireless/ath/ar5523/ar5523.c:275
> ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [inline]
> ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [inline]
> ar5523_probe+0xc66/0x1da0 drivers/net/wireless/ath/ar5523/ar5523.c:1655
>
>
> Link: https://syzkaller.appspot.com/bug?extid=1bc2c2afd44f820a669f
> Reported-and-tested-by: syzbot+1bc2c2afd44f820a669f@syzkaller.appspotmail.com
> Signed-off-by: Mazin Al Haddad <mazinalhaddad05@gmail.com>
> ---
> drivers/net/wireless/ath/ar5523/ar5523.c | 31 ++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ar5523/ar5523.c b/drivers/net/wireless/ath/ar5523/ar5523.c
> index 6f937d2cc126..5451bf9ab9fb 100644
> --- a/drivers/net/wireless/ath/ar5523/ar5523.c
> +++ b/drivers/net/wireless/ath/ar5523/ar5523.c
> @@ -1581,8 +1581,39 @@ static int ar5523_probe(struct usb_interface *intf,
> struct usb_device *dev = interface_to_usbdev(intf);
> struct ieee80211_hw *hw;
> struct ar5523 *ar;
> + struct usb_host_interface *host = intf->cur_altsetting;
> int error = -ENOMEM;
>
> + if (host->desc.bNumEndpoints != 4) {
> + dev_err(&dev->dev, "Wrong number of endpoints\n");
> + return -ENODEV;
> + }
> +
> + for (int i = 0; i < host->desc.bNumEndpoints; ++i) {
> + struct usb_endpoint_descriptor *ep = &host->endpoint[i].desc;
> + // Check for type of endpoint and direction.
> + switch (i) {
> + case 0:
> + case 1:
> + if ((ep->bEndpointAddress & USB_DIR_OUT) &&
> + ((ep->bmAttributes & USB_ENDPOINT_XFERTYPE_MASK)
> + == USB_ENDPOINT_XFER_BULK)){
Did you run your change through checkpatch?
> + dev_err(&dev->dev, "Wrong type of endpoints\n");
> + return -ENODEV;
> + }
> + break;
> + case 2:
> + case 3:
> + if ((ep->bEndpointAddress & USB_DIR_IN) &&
> + ((ep->bmAttributes & USB_ENDPOINT_XFERTYPE_MASK)
> + == USB_ENDPOINT_XFER_BULK)){
> + dev_err(&dev->dev, "Wrong type of endpoints\n");
> + return -ENODEV;
> + }
> + break;
> + }
We have usb helper functions for all of this, why not use them instead
of attempting to roll your own?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-24 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 22:24 [PATCH] ar5523: check endpoints type and direction in probe() Mazin Al Haddad
2022-08-24 6:04 ` Greg KH [this message]
2022-08-27 10:36 ` Mazin Al Haddad
2022-08-30 12:09 ` Greg KH
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=YwW/cw2cXLEd5xFo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mazinalhaddad05@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paskripkin@gmail.com \
--cc=pontus.fuchs@gmail.com \
--cc=syzbot+1bc2c2afd44f820a669f@syzkaller.appspotmail.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