mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: michael.christie@oracle.com
To: Wang Hai <wanghai38@huawei.com>,
	martin.petersen@oracle.com, himanshu.madhani@oracle.com,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: target: core: Fix null-ptr-deref in target_alloc_device()
Date: Fri, 11 Oct 2024 08:56:14 -0500	[thread overview]
Message-ID: <73007761-533f-43c3-a721-3dbaac741d41@oracle.com> (raw)
In-Reply-To: <20241011113444.40749-1-wanghai38@huawei.com>

On 10/11/24 6:34 AM, Wang Hai wrote:
> There is a null-ptr-deref issue reported by kasan:
> 
> BUG: KASAN: null-ptr-deref in target_alloc_device+0xbc4/0xbe0 [target_core_mod]
> ...
>  kasan_report+0xb9/0xf0
>  target_alloc_device+0xbc4/0xbe0 [target_core_mod]
>  core_dev_setup_virtual_lun0+0xef/0x1f0 [target_core_mod]
>  target_core_init_configfs+0x205/0x420 [target_core_mod]
>  do_one_initcall+0xdd/0x4e0
> ...
>  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> 
> In target_alloc_device(), if allocing memory for dev queues fails,
> then dev will be freed by dev->transport->free_device(), but
> dev->transport is not initialized at that time, which will lead to a
> null pointer reference problem.
> 
> Fixing this bug by freeing dev with hba->backend->ops->free_device().
> 
> Fixes: 1526d9f10c61 ("scsi: target: Make state_list per CPU")
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
> ---
>  drivers/target/target_core_device.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/target/target_core_device.c b/drivers/target/target_core_device.c
> index bf4892544cfd..bb84d304b07e 100644
> --- a/drivers/target/target_core_device.c
> +++ b/drivers/target/target_core_device.c
> @@ -691,7 +691,7 @@ struct se_device *target_alloc_device(struct se_hba *hba, const char *name)
>  
>  	dev->queues = kcalloc(nr_cpu_ids, sizeof(*dev->queues), GFP_KERNEL);
>  	if (!dev->queues) {
> -		dev->transport->free_device(dev);
> +		hba->backend->ops->free_device(dev);
>  		return NULL;
>  	}
>  

Thanks.

Reviewed-by: Mike Christie <michael.christie@oracle.com>

  reply	other threads:[~2024-10-11 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 11:34 Wang Hai
2024-10-11 13:56 ` michael.christie [this message]
2024-10-16  2:39 ` Martin K. Petersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73007761-533f-43c3-a721-3dbaac741d41@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=himanshu.madhani@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=target-devel@vger.kernel.org \
    --cc=wanghai38@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®