> -----Original Message-----
> From: Andrea Parri (Microsoft) <parri.and...@gmail.com>
> Sent: Wednesday, November 18, 2020 10:33 AM
> To: linux-ker...@vger.kernel.org
> Cc: KY Srinivasan <k...@microsoft.com>; Haiyang Zhang
> <haiya...@microsoft.com>; Stephen Hemminger
> <sthem...@microsoft.com>; Wei Liu <wei....@kernel.org>; linux-
> hyp...@vger.kernel.org; Michael Kelley <mikel...@microsoft.com>; Juan
> Vazquez <juv...@microsoft.com>; Saruhan Karademir
> <skar...@microsoft.com>; Andrea Parri (Microsoft)
> <parri.and...@gmail.com>; David S. Miller <da...@davemloft.net>; Jakub
> Kicinski <k...@kernel.org>; netdev@vger.kernel.org
> Subject: [PATCH] hv_netvsc: Validate number of allocated sub-channels
> 
> Lack of validation could lead to out-of-bound reads and information leaks (cf.
> usage of nvdev->chan_table[]).  Check that the number of allocated sub-
> channels fits into the expected range.
> 
> Suggested-by: Saruhan Karademir <skar...@microsoft.com>
> Signed-off-by: Andrea Parri (Microsoft) <parri.and...@gmail.com>
> Cc: "David S. Miller" <da...@davemloft.net>
> Cc: Jakub Kicinski <k...@kernel.org>
> Cc: netdev@vger.kernel.org
> ---
> Based on hyperv-next.
> 
>  drivers/net/hyperv/rndis_filter.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/net/hyperv/rndis_filter.c
> b/drivers/net/hyperv/rndis_filter.c
> index 3835d9bea1005..c5a709f67870f 100644
> --- a/drivers/net/hyperv/rndis_filter.c
> +++ b/drivers/net/hyperv/rndis_filter.c
> @@ -1226,6 +1226,11 @@ int rndis_set_subchannel(struct net_device *ndev,
>               return -EIO;
>       }
> 
> +     /* Check that number of allocated sub channel is within the expected
> range */
> +     if (init_packet->msg.v5_msg.subchn_comp.num_subchannels >
> nvdev->num_chn - 1) {
> +             netdev_err(ndev, "invalid number of allocated sub
> channel\n");
> +             return -EINVAL;
> +     }
>       nvdev->num_chn = 1 +
>               init_packet->msg.v5_msg.subchn_comp.num_subchannels;

Reviewed-by: Haiyang Zhang <haiya...@microsoft.com>
Thank you.

Reply via email to