From: mdshahid03@gmail.com
To: ketan.mukadam@broadcom.com
Cc: James.Bottomley@HansenPartnership.com, mkp@kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mohammad Shahid <mdshahid03@gmail.com>
Subject: [PATCH] scsi: be2iscsi: Fix NULL pointer dereference in memory cleanup
Date: Sat, 7 Nov 2026 15:06:11 +0530 [thread overview]
Message-ID: <20261107093611.42311-1-mdshahid03@gmail.com> (raw)
From: Mohammad Shahid <mdshahid03@gmail.com>
During memory allocation ,DMA memory may be allocated successfully
before the descriptor array allocation fails.
In this case ,mem_descr->mem_array is NULL,but cleanup path tries
to access it.
Use mem_arr_orig to free the DMA allocation of the current
descriptor and handle previously allocated descriptors separately.
Signed-off-by: Mohammad Shahid <mdshahid03@gmail.com>
---
drivers/scsi/be2iscsi/be_main.c | 34 ++++++++++++++++++++-------------
1 file changed, 21 insertions(+), 13 deletions(-)
diff --git a/drivers/scsi/be2iscsi/be_main.c b/drivers/scsi/be2iscsi/be_main.c
index fd18d4d3d219..95706b5db7be 100644
--- a/drivers/scsi/be2iscsi/be_main.c
+++ b/drivers/scsi/be2iscsi/be_main.c
@@ -2549,22 +2549,30 @@ static int beiscsi_alloc_mem(struct beiscsi_hba *phba)
kfree(mem_arr_orig);
return 0;
free_mem:
- mem_descr->num_elements = j;
- while ((i) || (j)) {
+ /* Free DMA allocations of the current descriptor */
+ for (; j > 0; j--) {
+ dma_free_coherent(&phba->pcidev->dev,
+ mem_arr_orig[j - 1].size,
+ mem_arr_orig[j - 1].virtual_address,
+ (unsigned long)
+ mem_arr_orig[j - 1].bus_address.u.a64.address);
+ }
+
+ /* Free previously completed descriptors */
+ while (i > 0) {
+ i--;
+ mem_descr--;
+
for (j = mem_descr->num_elements; j > 0; j--) {
dma_free_coherent(&phba->pcidev->dev,
- mem_descr->mem_array[j - 1].size,
- mem_descr->mem_array[j - 1].
- virtual_address,
- (unsigned long)mem_descr->
- mem_array[j - 1].
- bus_address.u.a64.address);
- }
- if (i) {
- i--;
- kfree(mem_descr->mem_array);
- mem_descr--;
+ mem_descr->mem_array[j - 1].size,
+ mem_descr->mem_array[j - 1].virtual_address,
+ (unsigned long)
+ mem_descr->mem_array[j - 1].bus_address.u.a64.address);
}
+
+ kfree(mem_descr->mem_array);
+
}
kfree(mem_arr_orig);
kfree(phba->init_mem);
--
2.43.0
reply other threads:[~2026-11-07 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261107093611.42311-1-mdshahid03@gmail.com \
--to=mdshahid03@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ketan.mukadam@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
/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®