Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sonali Pradhan <sonalipradhan@google.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_ncm: validate datagram bounds in ncm_unwrap_ntb()
Date: Fri, 3 Jul 2026 07:49:09 +0200	[thread overview]
Message-ID: <2026070359-uselessly-staging-f506@gregkh> (raw)
In-Reply-To: <20260703051945.1691028-1-sonalipradhan@google.com>

On Fri, Jul 03, 2026 at 05:19:45AM +0000, Sonali Pradhan wrote:
> When unpacking host-supplied NTBs, ncm_unwrap_ntb() checks datagram length
> against frame_max but does not verify that the datagram fits within the
> declared block length. Additionally, when decoding multiple NTBs from a
> single socket buffer, subsequent block lengths are not checked against the
> actual remaining buffer data.
> 
> With these checks missing, a malicious USB host can specify datagram
> offsets and lengths that point beyond the block, or supply secondary NTB
> headers declaring lengths larger than the buffer. skb_put_data() then
> copies adjacent kernel memory from skb_shared_info into the network skb.
> 
> Fix this by verifying that sufficient buffer space remains for the NTB
> header before parsing, handling zero-length block declarations, ensuring
> that block lengths never exceed the remaining buffer space, and verifying
> that each datagram payload stays strictly within the block boundary.
> 
> Fixes: 427694cfaafa ("usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call")
> Fixes: 2b74b0a04d3e ("USB: gadget: f_ncm: add bounds checks to ncm_unwrap_ntb()")
> Cc: stable@vger.kernel.org
> Assisted-by: Jetski:Gemini-2.5-Pro
> Signed-off-by: Sonali Pradhan <sonalipradhan@google.com>
> ---
>  drivers/usb/gadget/function/f_ncm.c | 17 +++++++++++++----
>  1 file changed, 13 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/gadget/function/f_ncm.c b/drivers/usb/gadget/function/f_ncm.c
> index c5bf8a448d64..64eabda2f546 100644
> --- a/drivers/usb/gadget/function/f_ncm.c
> +++ b/drivers/usb/gadget/function/f_ncm.c
> @@ -1189,6 +1189,10 @@ static int ncm_unwrap_ntb(struct gether *port,
>  	frame_max = ncm_opts->max_segment_size;
>  
>  parse_ntb:
> +	if (to_process < (int)opts->nth_size) {
> +		INFO(port->func.config->cdev, "Packet too small for headers\n");
> +		goto err;
> +	}
>  	tmp = (__le16 *)ntb_ptr;
>  
>  	/* dwSignature */
> @@ -1209,8 +1213,12 @@ static int ncm_unwrap_ntb(struct gether *port,
>  	tmp++; /* skip wSequence */
>  
>  	block_len = get_ncm(&tmp, opts->block_length);
> +	if (block_len == 0)
> +		block_len = to_process;
> +
>  	/* (d)wBlockLength */
> -	if ((block_len < opts->nth_size + opts->ndp_size) || (block_len > ntb_max)) {
> +	if ((block_len < opts->nth_size + opts->ndp_size) || (block_len > ntb_max) ||
> +			(block_len > to_process)) {
>  		INFO(port->func.config->cdev, "Bad block length: %#X\n", block_len);
>  		goto err;
>  	}
> @@ -1273,7 +1281,7 @@ static int ncm_unwrap_ntb(struct gether *port,
>  			index = index2;
>  			/* wDatagramIndex[0] */
>  			if ((index < opts->nth_size) ||
> -					(index > block_len - opts->dpe_size)) {
> +					(index > block_len)) {
>  				INFO(port->func.config->cdev,
>  				     "Bad index: %#X\n", index);
>  				goto err;
> @@ -1285,7 +1293,8 @@ static int ncm_unwrap_ntb(struct gether *port,
>  			 * ethernet hdr + crc or larger than max frame size
>  			 */
>  			if ((dg_len < 14 + crc_len) ||
> -					(dg_len > frame_max)) {
> +					(dg_len > frame_max) ||
> +					(dg_len > block_len - index)) {
>  				INFO(port->func.config->cdev,
>  				     "Bad dgram length: %#X\n", dg_len);
>  				goto err;
> @@ -1310,7 +1319,7 @@ static int ncm_unwrap_ntb(struct gether *port,
>  			dg_len2 = get_ncm(&tmp, opts->dgram_item_len);
>  
>  			/* wDatagramIndex[1] */
> -			if (index2 > block_len - opts->dpe_size) {
> +			if (index2 > block_len) {
>  				INFO(port->func.config->cdev,
>  				     "Bad index: %#X\n", index2);
>  				goto err;
> -- 
> 2.55.0.rc0.799.gd6f94ed593-goog
> 
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2026-07-03  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  5:19 [PATCH] usb: gadget: f_ncm: validate datagram bounds in ncm_unwrap_ntb() Sonali Pradhan
2026-07-03  5:49 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-03  8:37 Sonali Pradhan

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=2026070359-uselessly-staging-f506@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=sonalipradhan@google.com \
    --cc=stable@vger.kernel.org \
    /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