From: Oliver Neukum <oneukum@suse.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: KASAN reporting bug in ath6kl
Date: Mon, 29 Jul 2019 14:58:08 +0200 [thread overview]
Message-ID: <1564405088.25582.13.camel@suse.com> (raw)
Hi,
I am looking at this report:
Title: general protection fault in
ath6kl_usb_alloc_urb_from_pipe
Last occurred: 0 days ago
Reported: 102 days ago
Branches: Mainline (with usb-fuzzer patches)
Dashboard link: https://syzkaller.appspot.com/bug?id=cd8b9cfe50a0bf
36ee19eda2d7e2e06843dfbeaf
Original thread: https://lkml.kernel.org/lkml/0000000000008e82510586
5615e3@google.com/T/#u
This bug has a C reproducer.
No one replied to the original thread for this bug.
This looks like a bug in a net/wireless USB driver.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+ead4037ec793e025e66f@syzkaller.appspotmail.com
--
It looks like a bug in
static int ath6kl_usb_setup_pipe_resources(struct ath6kl_usb *ar_usb)
to me, which happily does nothing if the device has no endpoints.
THis needs sanity checking, but it looks like the driver
really uses 8 endpoints. Can you confirm that all 8 of them
are indeed needed?
Regards
Oliver
reply other threads:[~2019-07-29 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1564405088.25582.13.camel@suse.com \
--to=oneukum@suse.com \
--cc=kvalo@codeaurora.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).