[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25336478fe5bca68b6c7d2c37766a9f98f6c7ad1.camel@kernel.org>
Date: Mon, 28 Sep 2020 16:22:33 -0700
From: Saeed Mahameed <saeed@...nel.org>
To: "Gustavo A. R. Silva" <gustavoars@...nel.org>,
Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Roi Dayan <roid@...lanox.com>, Vlad Buslov <vladbu@...dia.com>,
Ariel Levkovich <lariel@...lanox.com>
Cc: netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] net/mlx5e: Fix potential null pointer dereference
On Fri, 2020-09-25 at 11:49 -0500, Gustavo A. R. Silva wrote:
> Calls to kzalloc() and kvzalloc() should be null-checked
> in order to avoid any potential failures. In this case,
> a potential null pointer dereference.
>
> Fix this by adding null checks for _parse_attr_ and _flow_
> right after allocation.
>
> Addresses-Coverity-ID: 1497154 ("Dereference before null check")
> Fixes: c620b772152b ("net/mlx5: Refactor tc flow attributes
> structure")
> Signed-off-by: Gustavo A. R. Silva <gustavoars@...nel.org>
> ---
>
Applied to net-next-mlx5.
Thanks.
Powered by blists - more mailing lists