From: yebin <yebin10@huawei.com>
To: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] scsi: be2iscsi: fix null-ptr-deref in beiscsi_alloc_mem
Date: Thu, 25 Aug 2022 19:26:07 +0800 [thread overview]
Message-ID: <63075C4F.3010506@huawei.com> (raw)
In-Reply-To: <20220727072132.3906922-1-yebin10@huawei.com>
ping...
On 2022/7/27 15:21, Ye Bin wrote:
> Coccicheck report follow issue:
> ./drivers/scsi/be2iscsi/be_main.c:2561:37-41: ERROR: mem_descr -> mem_array is NULL but dereferenced.
> ./drivers/scsi/be2iscsi/be_main.c:2563:9-24: ERROR: mem_descr -> mem_array is NULL but dereferenced.
> ./drivers/scsi/be2iscsi/be_main.c:2566:9-20: ERROR: mem_descr -> mem_array is NULL but dereferenced.
>
> If goto free_mem, that's mean last "mem_descr->mem_array" is NULL. However,
> to avoid resource there will set "mem_descr->num_elements" with "j" which
> maybe non-zero. Then will lead to null-ptr-deref when free dma resource.
>
> To solved above issue set "mem_descr->mem_array" with "mem_arr_orig"
> when free memory.
>
> Signed-off-by: Ye Bin <yebin10@huawei.com>
> ---
> drivers/scsi/be2iscsi/be_main.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/be2iscsi/be_main.c b/drivers/scsi/be2iscsi/be_main.c
> index 50a577ac3bb4..08f856447b4a 100644
> --- a/drivers/scsi/be2iscsi/be_main.c
> +++ b/drivers/scsi/be2iscsi/be_main.c
> @@ -2540,13 +2540,13 @@ static int beiscsi_alloc_mem(struct beiscsi_hba *phba)
> mem_arr++;
> }
> } while (alloc_size);
> - mem_descr->num_elements = j;
> - mem_descr->size_in_bytes = phba->mem_req[i];
> mem_descr->mem_array = kmalloc_array(j, sizeof(*mem_arr),
> GFP_KERNEL);
> if (!mem_descr->mem_array)
> goto free_mem;
>
> + mem_descr->num_elements = j;
> + mem_descr->size_in_bytes = phba->mem_req[i];
> memcpy(mem_descr->mem_array, mem_arr_orig,
> sizeof(struct mem_array) * j);
> mem_descr++;
> @@ -2554,7 +2554,11 @@ static int beiscsi_alloc_mem(struct beiscsi_hba *phba)
> kfree(mem_arr_orig);
> return 0;
> free_mem:
> - mem_descr->num_elements = j;
> + if (j) {
> + mem_descr->num_elements = j;
> + mem_descr->mem_array = mem_arr_orig;
> + mem_arr_orig = NULL;
> + }
> while ((i) || (j)) {
> for (j = mem_descr->num_elements; j > 0; j--) {
> dma_free_coherent(&phba->pcidev->dev,
prev parent reply other threads:[~2022-08-25 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:21 [PATCH -next] scsi: be2iscsi: fix null-ptr-deref in beiscsi_alloc_mem Ye Bin
2022-08-25 11:26 ` yebin [this message]
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=63075C4F.3010506@huawei.com \
--to=yebin10@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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