From: Bean Huo <beanhuo@iokpp.de>
To: Stanley Jhu <stanleyjhu@google.com>,
"Martin K. Petersen" <mkp@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: powenkao@google.com, Alim Akhtar <alim.akhtar@samsung.com>,
Bart Van Assche <bvanassche@acm.org>,
Bean Huo <beanhuo@micron.com>,
Peter Wang <peter.wang@mediatek.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi: ufs: bsg: Validate request_len before accessing request
Date: Wed, 14 Oct 2026 12:02:36 +0200 [thread overview]
Message-ID: <4275c168417c7f5b8f89f06dc15b7459a6346ec0.camel@iokpp.de> (raw)
In-Reply-To: <20261013102913.948718-2-stanleyjhu@google.com>
On Tue, 2026-10-13 at 18:29 +0800, Stanley Jhu wrote:
> ufs_bsg_request() and ufs_bsg_exec_advanced_rpmb_req() read the
> request buffer without checking job->request_len, which userspace
> controls. A short request causes an out-of-bounds read. Found by
> syzkaller.
>
> Reject requests shorter than the structure each path reads.
>
> Fixes: 64d4864714c2 ("scsi: ufs: bsg: Remove unnecessary length checkup")
> Fixes: 6ff265fc5ef6 ("scsi: ufs: core: bsg: Add advanced RPMB support in
> ufs_bsg")
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanley Jhu <stanleyjhu@google.com>
> ---
> drivers/ufs/core/ufs_bsg.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/ufs/core/ufs_bsg.c b/drivers/ufs/core/ufs_bsg.c
> index 7a66917b3fc0..dab1f05aff38 100644
> --- a/drivers/ufs/core/ufs_bsg.c
> +++ b/drivers/ufs/core/ufs_bsg.c
> @@ -73,6 +73,9 @@ static int ufs_bsg_exec_advanced_rpmb_req(struct ufs_hba
> *hba, struct bsg_job *j
> if (hba->ufs_version < ufshci_version(4, 0) || !hba-
> >dev_info.b_advanced_rpmb_en)
> return -EINVAL;
>
> + if (job->request_len < sizeof(*rpmb_request))
> + return -EINVAL;
> +
> if (rpmb_request->ehs_req.length != 2 || rpmb_request-
> >ehs_req.ehs_type != 1)
> return -EINVAL;
>
> @@ -142,6 +145,11 @@ static int ufs_bsg_request(struct bsg_job *job)
>
> bsg_reply->reply_payload_rcv_len = 0;
>
> + if (job->request_len < sizeof(*let )) {
> + bsg_reply->result = -EINVAL;
> + return -EINVAL;
> + }
> +
> ufshcd_rpm_get_sync(hba);
>
> msgcode = bsg_request->msgcode;
Stanley,
The check was removed by my commit 64d4864714c2 when adding arpmb support, since
msgcode check was thought to be enough, thanks for fixing it.
Reviewed-by: Bean Huo <beanhuo@micron.com>
next prev parent reply other threads:[~2026-10-14 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 10:29 [PATCH 0/3] scsi: ufs: Fix UIC result byte and BSG request length handling Stanley Jhu
2026-10-13 10:29 ` [PATCH 1/3] scsi: ufs: bsg: Validate request_len before accessing request Stanley Jhu
2026-10-14 10:02 ` Bean Huo [this message]
2026-10-13 10:29 ` [PATCH 2/3] scsi: ufs: bsg: Clear the UIC result byte before sending UIC commands Stanley Jhu
2026-10-14 7:28 ` Peter Wang
2026-10-14 10:43 ` Bean Huo
2026-10-14 13:30 ` Bart Van Assche
2026-10-13 10:29 ` [PATCH 3/3] scsi: ufs: core: Clear stale UIC result byte before peer DME retries Stanley Jhu
2026-10-14 10:58 ` 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=4275c168417c7f5b8f89f06dc15b7459a6346ec0.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=peter.wang@mediatek.com \
--cc=powenkao@google.com \
--cc=stable@vger.kernel.org \
--cc=stanleyjhu@google.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®