[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025071026-fanciness-size-1d5d@gregkh>
Date: Thu, 10 Jul 2025 10:21:46 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: jackysliu <1972843537@...com>
Cc: viro@...iv.linux.org.uk, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: gadget: functioni: Fix a oob problem in rndis
On Thu, Jul 10, 2025 at 04:14:18PM +0800, jackysliu wrote:
> A critical out-of-bounds memory access vulnerability exists in the RNDIS
> (Remote Network Driver Interface Specification) implementation.
It's not really "critical" as the specification never claims to be
secure at all, and we have said for years that you should never run this
on system that you do not fully trust (host and client.)
> The vulnerability stems from insufficient boundary validation when
> processing SET requests with user-controlled InformationBufferOffset
> and InformationBufferLength parameters.
>
> The vulnerability can be fixed by adding addtional boundary checks
>
> Signed-off-by: jackysliu <1972843537@...com>
Please use a full name, not just a one word alias.
And what commit id does this fix?
> ---
> drivers/usb/gadget/function/rndis.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/function/rndis.c b/drivers/usb/gadget/function/rndis.c
> index afd75d72412c..cc522fb4c06c 100644
> --- a/drivers/usb/gadget/function/rndis.c
> +++ b/drivers/usb/gadget/function/rndis.c
> @@ -641,7 +641,8 @@ static int rndis_set_response(struct rndis_params *params,
> BufOffset = le32_to_cpu(buf->InformationBufferOffset);
> if ((BufLength > RNDIS_MAX_TOTAL_SIZE) ||
> (BufOffset > RNDIS_MAX_TOTAL_SIZE) ||
> - (BufOffset + 8 >= RNDIS_MAX_TOTAL_SIZE))
> + (BufOffset + 8 >= RNDIS_MAX_TOTAL_SIZE) ||
> + (BufOffset + BufLength+8 > RNDIS_MAX_TOTAL_SIZE))
> return -EINVAL;
>
> r = rndis_add_response(params, sizeof(rndis_set_cmplt_type));
> --
> 2.43.5
>
As I asked before, please run scripts/checkpatch.pl on your patch and
fix the issue it found. Can you do all of this and send a v2 patch?
thanks,
greg k-h
Powered by blists - more mailing lists