Linux USB
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Tristan Madani <tristmd@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kevin Lloyd <linux@sierrawireless.com>,
	linux-usb@vger.kernel.org, stable@vger.kernel.org,
	Tristan Madani <tristan@talencesecurity.com>
Subject: Re: [PATCH v2] USB: serial: sierra: validate URB length in instat callback
Date: Thu, 29 Oct 2026 16:09:31 +0100	[thread overview]
Message-ID: <auNhq32ChleGKQWz@hovoldconsulting.com> (raw)
In-Reply-To: <20261019103849.3716324-1-tristmd@gmail.com>

On Mon, Oct 19, 2026 at 10:38:49AM +0000, Tristan Madani wrote:
> From: Tristan Madani <tristan@talencesecurity.com>
> 
> sierra_instat_callback() reads request fields and one byte past the
> usb_ctrlrequest header without first checking that urb->actual_length
> is large enough.  A short USB interrupt transfer could cause an
> out-of-bounds read.
> 
> Add two length checks matching the pattern already present in the
> option driver (option_instat_callback): one for the request header
> before accessing bRequestType, and one for the line-state data byte
> inside the serial-state notification handler.  Use dev_err() since
> failing these checks causes the interrupt URB not to be resubmitted.
> 
> Fixes: 033a3fb980b041 ("USB: Sierra Wireless driver update")
> Cc: stable@vger.kernel.org
> Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
> ---
> Changes in v2 (Johan Hovold):
>  - Split into two checks: one for the header before accessing
>    bRequestType, and one for the line-state data byte inside
>    the serial-state handler, matching the option driver pattern
>  - Use dev_err() instead of dev_dbg() since early return prevents
>    further interrupts

Thanks for the update.

Now applied, with one change below.

>  drivers/usb/serial/sierra.c | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/serial/sierra.c b/drivers/usb/serial/sierra.c
> index 6e443aacae07d..03ed76dfbb2e3 100644
> --- a/drivers/usb/serial/sierra.c
> +++ b/drivers/usb/serial/sierra.c
> @@ -575,10 +575,23 @@ static void sierra_instat_callback(struct urb *urb)
>  				__func__);
>  			return;
>  		}
> +		if (urb->actual_length < sizeof(*req_pkt)) {
> +			dev_err(&port->dev, "%s: short transfer\n",
> +				__func__);
> +			return;
> +		}
>  		if ((req_pkt->bRequestType == 0xA1) &&
>  				(req_pkt->bRequest == 0x20)) {
>  			int old_dcd_state;
> -			unsigned char signals = *((unsigned char *)
> +			unsigned char signals;
> +
> +			if (urb->actual_length < sizeof(*req_pkt) + 1) {
> +				dev_err(&port->dev,
> +					"%s: short interrupt transfer\n",
> +					__func__);
> +				return;
> +			}
> +			signals = *((unsigned char *)
>  					urb->transfer_buffer +
>  					sizeof(struct usb_ctrlrequest));

I used sizeof(*req_pkt) here too for consistency.

Johan

      parent reply	other threads:[~2026-10-29 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:38 [PATCH v2] USB: serial: sierra: validate URB length in instat callback Tristan Madani
2026-10-19 10:40 ` sashiko-bot
2026-10-29 15:09 ` Johan Hovold [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=auNhq32ChleGKQWz@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@sierrawireless.com \
    --cc=stable@vger.kernel.org \
    --cc=tristan@talencesecurity.com \
    --cc=tristmd@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