From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: co <co+66c3f58096d0bde8@bugs.sh>
Cc: linux-usb@vger.kernel.org,
Valentina Manea <valentina.manea.m@gmail.com>,
Shuah Khan <shuah@kernel.org>, Hongren Zheng <i@zenithal.me>,
Suwan Kim <suwan.kim027@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] drivers/usb: NULL pointer dereference in stub_recv_cmd_submit()
Date: Sat, 12 Sep 2026 07:47:00 +0200 [thread overview]
Message-ID: <2026091217-almighty-slouching-de2c@gregkh> (raw)
In-Reply-To: <J3vQPnNHSkQ6YUiFvu1bk8ai3Q8aZ7a9J1Y7@bugs.sh>
On Sat, Sep 12, 2026 at 02:06:13AM +0000, co wrote:
> This is a bug report, not a patch submission. See
> https://bugs.sh/reporting.html
>
> We found a bug reachable in:
>
> path drivers/usb/usbip
> crash NULL pointer dereference in stub_recv_cmd_submit()
> commit 2f1baf1fc892 ("Merge tag 'trace-v7.2-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace")
>
> Config, environment, the sanitizer report and a C reproducer follow.
>
> == Notes ===============================================================
> If you fix this bug, this tag credits the report and lets us
> close it on our side:
>
> Reported-by: co+66c3f58096d0bde8@bugs.sh
>
> Everything in this mail is validated by the reproducer below.
>
> We also hold an unreviewed LLM-generated analysis and candidate
> patch. The same reproducer panics the unpatched kernel and runs
> clean with that patch applied. Use it as a starting point, or ignore
> it and write your own:
>
> patch.diff https://bugs.sh/b/66c3f58096d0bde8/patch.diff
Please just submit patches like normal, in a format that can be applied,
and do not make us go to random links to attempt to get any information.
That's not how kernel development works at all.
thanks,
greg k-h
next prev parent reply other threads:[~2026-09-12 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 2:06 co
2026-09-12 5:47 ` Greg Kroah-Hartman [this message]
2026-09-12 18:41 ` Xiang Mei
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=2026091217-almighty-slouching-de2c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=co+66c3f58096d0bde8@bugs.sh \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=suwan.kim027@gmail.com \
--cc=valentina.manea.m@gmail.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®