From: Greg KH <gregkh@linuxfoundation.org>
To: 江世昊 <sh.jiang@zju.edu.cn>
Cc: security@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: [bug report] usb: WARNING in usb_free_urb
Date: Wed, 18 Dec 2024 08:30:22 +0100 [thread overview]
Message-ID: <2024121824-twine-ageless-5c7c@gregkh> (raw)
In-Reply-To: <ee535ac.6def.193d8967e04.Coremail.sh.jiang@zju.edu.cn>
On Wed, Dec 18, 2024 at 03:06:01PM +0800, 江世昊 wrote:
> Hello developers,
>
> We hit this issue when fuzzing the usb module with Syzkaller.
Great! But why are you using an old kernel version:
> HEAD commit: 819837584309 6.12.0-rc5
If you come up with a fix for this, please submit it as you have a
reproducer.
Also, no need to cc: the security alias if you also send it to public
lists like this.
thanks,
greg k-h
prev parent reply other threads:[~2024-12-18 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 7:06 [bug report] usb: WARNING in usb_free_urb 江世昊
2024-12-18 7:30 ` 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=2024121824-twine-ageless-5c7c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=security@kernel.org \
--cc=sh.jiang@zju.edu.cn \
--cc=syzkaller@googlegroups.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