From: Shuah Khan <skhan@linuxfoundation.org>
To: Weiming Shi <bestswngs@gmail.com>,
Valentina Manea <valentina.manea.m@gmail.com>,
Shuah Khan <shuah@kernel.org>, Hongren Zheng <i@zenithal.me>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Suwan Kim <suwan.kim027@gmail.com>,
co+66c3f58096d0bde8@bugs.sh, Xiang Mei <xmei5@asu.edu>,
stable@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] usbip: stub: keep URB array state consistent on errors
Date: Wed, 23 Sep 2026 03:29:50 -0600 [thread overview]
Message-ID: <c80ca0bc-1398-4f6f-bfcc-c49089a51082@linuxfoundation.org> (raw)
In-Reply-To: <20260912083925.587987-2-bestswngs@gmail.com>
On 9/12/26 02:39, Weiming Shi wrote:
> stub_priv_alloc() links a zeroed stub_priv to priv_init before the URB
> array is allocated. The error handler may therefore consume the object
> after stub_recv_cmd_submit() reports SDEV_EVENT_ERROR_MALLOC.
>
> Do not publish num_urbs until the array exists. If a later URB allocation
> fails, clear the freed array pointer and count before the event handler can
> walk them. This prevents a NULL dereference on array-allocation failure
> and freed-array reads that can lead to invalid URB use or a double free on
> later failures.
How is this problem reproduced? Why is this a problem in this code path?
>
> Fixes: ea44d190764b ("usbip: Implement SG support to vhci-hcd and stub driver")
> Cc: stable@vger.kernel.org # 5.4+
> Reported-by: co+66c3f58096d0bde8@bugs.sh
> Closes: https://lore.kernel.org/all/J3vQPnNHSkQ6YUiFvu1bk8ai3Q8aZ7a9J1Y7%40bugs.sh/
> Assisted-by: Codex:gpt-5
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
> drivers/usb/usbip/stub_rx.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/usbip/stub_rx.c b/drivers/usb/usbip/stub_rx.c
> index 1e9ae578810d9..33058fb05b2f4 100644
> --- a/drivers/usb/usbip/stub_rx.c
> +++ b/drivers/usb/usbip/stub_rx.c
> @@ -534,10 +534,10 @@ static void stub_recv_cmd_submit(struct stub_device *sdev,
> }
>
> /* allocate urb array */
> - priv->num_urbs = num_urbs;
> priv->urbs = kmalloc_objs(*priv->urbs, num_urbs);
> if (!priv->urbs)
> goto err_urbs;
> + priv->num_urbs = num_urbs;
>
> /* setup a urb */
> if (support_sg) {
> @@ -641,6 +641,8 @@ static void stub_recv_cmd_submit(struct stub_device *sdev,
>
> err_urb:
> kfree(priv->urbs);
> + priv->urbs = NULL;
> + priv->num_urbs = 0;
> err_urbs:
> kfree(buffer);
> sgl_free(sgl);
thanks,
-- Shuah
prev parent reply other threads:[~2026-09-23 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 8:39 Weiming Shi
2026-09-23 9:29 ` Shuah Khan [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=c80ca0bc-1398-4f6f-bfcc-c49089a51082@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bestswngs@gmail.com \
--cc=co+66c3f58096d0bde8@bugs.sh \
--cc=gregkh@linuxfoundation.org \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=suwan.kim027@gmail.com \
--cc=valentina.manea.m@gmail.com \
--cc=xmei5@asu.edu \
/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®