From: Oliver Neukum <oneukum@suse.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Rex Nie <rex.nie@jaguarmicro.com>, Jann Horn <jannh@google.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: core: replace kmalloc + copy_from_user with memdup_user
Date: Wed, 8 Oct 2025 23:23:59 +0200 [thread overview]
Message-ID: <71613c2a-73d5-4f6e-a71b-03a2aa0f7bdf@suse.com> (raw)
In-Reply-To: <20250919115654.1011141-2-thorsten.blum@linux.dev>
Hi,
On 19.09.25 13:56, Thorsten Blum wrote:
> Replace kmalloc() followed by copy_from_user() with memdup_user() to
> simplify and improve proc_do_submiturb(). Replace the hard-coded 8 bytes
> with the size of 'struct usb_ctrlrequest'.
>
> Return early if an error occurs, and avoid manually setting 'ret' and
> using 'goto error'.
>
> No functional changes intended.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> drivers/usb/core/devio.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
> index f6ce6e26e0d4..3bc54a5c59ff 100644
> --- a/drivers/usb/core/devio.c
> +++ b/drivers/usb/core/devio.c
> @@ -1670,13 +1670,9 @@ static int proc_do_submiturb(struct usb_dev_state *ps, struct usbdevfs_urb *uurb
> /* min 8 byte setup packet */
> if (uurb->buffer_length < 8)
> return -EINVAL;
> - dr = kmalloc(sizeof(struct usb_ctrlrequest), GFP_KERNEL);
> - if (!dr)
> - return -ENOMEM;
> - if (copy_from_user(dr, uurb->buffer, 8)) {
> - ret = -EFAULT;
> - goto error;
> - }
> + dr = memdup_user(uurb->buffer, sizeof(struct usb_ctrlrequest));
You cannot do this. User space cannot and must not know or care how long
struct usb_ctrlrequest is. It is a data structure internal to the kernel.
For the purpose of this API we copy 8 bytes. That is set in stone.
If the kernel's data structure ever changes length, we will have
to define a new ioctl.
You have to leave the literal 8.
Regards
Oliver
prev parent reply other threads:[~2025-10-08 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 11:56 [PATCH] USB: core: replace kmalloc + copy_from_user with memdup_user Thorsten Blum
2025-10-08 11:05 ` Greg Kroah-Hartman
2025-10-08 21:23 ` Oliver Neukum [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=71613c2a-73d5-4f6e-a71b-03a2aa0f7bdf@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rex.nie@jaguarmicro.com \
--cc=stern@rowland.harvard.edu \
--cc=thorsten.blum@linux.dev \
/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