From: Bean Huo <huobean@gmail.com>
To: alim.akhtar@samsung.com, avri.altman@wdc.com,
asutoshd@codeaurora.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
cang@codeaurora.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 3/5] scsi: ufs: fix potential access NULL pointer while memcpy
Date: Sun, 31 May 2020 17:08:29 +0200 [thread overview]
Message-ID: <20200531150831.9946-4-huobean@gmail.com> (raw)
In-Reply-To: <20200531150831.9946-1-huobean@gmail.com>
From: Bean Huo <beanhuo@micron.com>
If param_offset is not 0, the memcpy length shouldn't be the
true descriptor length.
Fixes: a4b0e8a4e92b ("scsi: ufs: Factor out ufshcd_read_desc_param")
Signed-off-by: Bean Huo <beanhuo@micron.com>
---
drivers/scsi/ufs/ufshcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index f7e8bfefe3d4..bc52a0e89cd3 100644
--- a/drivers/scsi/ufs/ufshcd.c
+++ b/drivers/scsi/ufs/ufshcd.c
@@ -3211,7 +3211,7 @@ int ufshcd_read_desc_param(struct ufs_hba *hba,
/* Check wherher we will not copy more data, than available */
if (is_kmalloc && param_size > buff_len)
- param_size = buff_len;
+ param_size = buff_len - param_offset;
if (is_kmalloc)
memcpy(param_read_buf, &desc_buf[param_offset], param_size);
--
2.17.1
next prev parent reply other threads:[~2020-05-31 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 15:08 [PATCH v4 0/5] scsi: ufs: cleanup ufs initialization Bean Huo
2020-05-31 15:08 ` [PATCH v4 1/5] scsi: ufs: remove max_t in ufs_get_device_desc Bean Huo
2020-05-31 15:08 ` [PATCH v4 2/5] scsi: ufs: delete ufshcd_read_desc() Bean Huo
2020-05-31 15:08 ` Bean Huo [this message]
2020-06-01 6:25 ` [PATCH v4 3/5] scsi: ufs: fix potential access NULL pointer while memcpy Avri Altman
2020-06-02 11:35 ` Bean Huo
2020-06-02 12:25 ` Avri Altman
2020-06-02 13:38 ` Avri Altman
2020-05-31 15:08 ` [PATCH v4 4/5] scsi: ufs: cleanup ufs initialization path Bean Huo
2020-05-31 15:08 ` [PATCH v4 5/5] scsi: ufs: add compatibility with 3.1 UFS unit descriptor length Bean Huo
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=20200531150831.9946-4-huobean@gmail.com \
--to=huobean@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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