[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180327.103911.924179090835764688.davem@davemloft.net>
Date: Tue, 27 Mar 2018 10:39:11 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: colin.king@...onical.com
Cc: dan.carpenter@...cle.com, sam@...dozajonas.com,
netdev@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net/ncsi: check for null return from call to
nla_nest_start
From: Colin King <colin.king@...onical.com>
Date: Mon, 26 Mar 2018 12:27:12 +0100
> From: Colin Ian King <colin.king@...onical.com>
>
> The call to nla_nest_start calls nla_put which can lead to a NULL
> return so it's possible for attr to become NULL and we can potentially
> get a NULL pointer dereference on attr. Fix this by checking for
> a NULL return.
>
> Detected by CoverityScan, CID#1466125 ("Dereference null return")
>
> Fixes: 955dc68cb9b2 ("net/ncsi: Add generic netlink family")
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
Applied, but...
Colin, please start marking your Subject lines properly with "[PATCH
net-next]" for patches targetting net-next as opposed to net.
Thank you.
Powered by blists - more mailing lists