linux-kernel - RE: [PATCH] platform/mellanox: mlxreg-hotplug: Check pointer for NULL before dereferencing it

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <BN9PR12MB538106C733D231B73FC1C1AAAF5A2@BN9PR12MB5381.namprd12.prod.outlook.com>
Date: Mon, 26 Feb 2024 15:15:14 +0000
From: Vadim Pasternak <vadimp@...dia.com>
To: Daniil Dulov <d.dulov@...ddin.ru>, Hans de Goede <hdegoede@...hat.com>
CC: Mark Gross <mgross@...ux.intel.com>, Andy Shevchenko <andy@...radead.org>,
	Darren Hart <dvhart@...radead.org>, "platform-driver-x86@...r.kernel.org"
	<platform-driver-x86@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "lvc-project@...uxtesting.org"
	<lvc-project@...uxtesting.org>
Subject: RE: [PATCH] platform/mellanox: mlxreg-hotplug: Check pointer for NULL
 before dereferencing it



> -----Original Message-----
> From: Daniil Dulov <d.dulov@...ddin.ru>
> Sent: Monday, 26 February 2024 16:55
> To: Hans de Goede <hdegoede@...hat.com>
> Cc: Daniil Dulov <d.dulov@...ddin.ru>; Mark Gross
> <mgross@...ux.intel.com>; Andy Shevchenko <andy@...radead.org>; Darren
> Hart <dvhart@...radead.org>; Vadim Pasternak <vadimp@...dia.com>;
> platform-driver-x86@...r.kernel.org; linux-kernel@...r.kernel.org; lvc-
> project@...uxtesting.org
> Subject: [PATCH] platform/mellanox: mlxreg-hotplug: Check pointer for NULL
> before dereferencing it
> 
> mlxreg_hotplug_work_helper() implies that item can be NULL. There is a
> sanity check that checks item for NULL and then dereferences it.
> 
> Even though, the comment before sanity check says that it can only happen if
> some piece of hardware is broken, but in this case it will lead to NULL-pointer
> dereference before the function is even called, so let's check it before
> dereferencing.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Fixes: c6acad68eb2d ("platform/mellanox: mlxreg-hotplug: Modify to use a
> regmap interface")
> Signed-off-by: Daniil Dulov <d.dulov@...ddin.ru>
> ---
>  drivers/platform/mellanox/mlxreg-hotplug.c | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> diff --git a/drivers/platform/mellanox/mlxreg-hotplug.c
> b/drivers/platform/mellanox/mlxreg-hotplug.c
> index 5c022b258f91..524121b9f070 100644
> --- a/drivers/platform/mellanox/mlxreg-hotplug.c
> +++ b/drivers/platform/mellanox/mlxreg-hotplug.c
> @@ -348,20 +348,6 @@ mlxreg_hotplug_work_helper(struct
> mlxreg_hotplug_priv_data *priv,
>  	u32 regval, bit;
>  	int ret;
> 
> -	/*
> -	 * Validate if item related to received signal type is valid.
> -	 * It should never happen, excepted the situation when some
> -	 * piece of hardware is broken. In such situation just produce
> -	 * error message and return. Caller must continue to handle the
> -	 * signals from other devices if any.
> -	 */
> -	if (unlikely(!item)) {
> -		dev_err(priv->dev, "False signal: at offset:mask
> 0x%02x:0x%02x.\n",
> -			item->reg, item->mask);
> -
> -		return;
> -	}

It would be enough just to produce dev_err(priv->dev, "False signal\n");
And return.

> -
>  	/* Mask event. */
>  	ret = regmap_write(priv->regmap, item->reg +
> MLXREG_HOTPLUG_MASK_OFF,
>  			   0);
> @@ -556,7 +542,7 @@ static void mlxreg_hotplug_work_handler(struct
> work_struct *work)
> 
>  	/* Handle topology and health configuration changes. */
>  	for (i = 0; i < pdata->counter; i++, item++) {
> -		if (aggr_asserted & item->aggr_mask) {
> +		if (item && (aggr_asserted & item->aggr_mask)) {
>  			if (item->health)
>  				mlxreg_hotplug_health_work_helper(priv,
> item);
>  			else
> --
> 2.25.1