From: Sumit Garg <sumit.garg@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] tee: qcom: prevent potential off by one read
Date: Fri, 19 Sep 2025 10:51:01 +0530 [thread overview]
Message-ID: <aMzoPc67ws5NMpKS@sumit-X1> (raw)
In-Reply-To: <aMvV4kK386Sni10i@stanley.mountain>
On Thu, Sep 18, 2025 at 12:50:26PM +0300, Dan Carpenter wrote:
> Re-order these checks to check if "i" is a valid array index before using
> it. This prevents a potential off by one read access.
>
> Fixes: d6e290837e50 ("tee: add Qualcomm TEE driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> drivers/tee/qcomtee/call.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
>
> diff --git a/drivers/tee/qcomtee/call.c b/drivers/tee/qcomtee/call.c
> index cc17a48d0ab7..ac134452cc9c 100644
> --- a/drivers/tee/qcomtee/call.c
> +++ b/drivers/tee/qcomtee/call.c
> @@ -308,7 +308,7 @@ static int qcomtee_params_from_args(struct tee_param *params,
> }
>
> /* Release any IO and OO objects not processed. */
> - for (; u[i].type && i < num_params; i++) {
> + for (; i < num_params && u[i].type; i++) {
> if (u[i].type == QCOMTEE_ARG_TYPE_OO ||
> u[i].type == QCOMTEE_ARG_TYPE_IO)
> qcomtee_object_put(u[i].o);
> --
> 2.51.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] tee: qcom: prevent potential off by one read
Date: Fri, 19 Sep 2025 10:51:01 +0530 [thread overview]
Message-ID: <aMzoPc67ws5NMpKS@sumit-X1> (raw)
In-Reply-To: <aMvV4kK386Sni10i@stanley.mountain>
On Thu, Sep 18, 2025 at 12:50:26PM +0300, Dan Carpenter wrote:
> Re-order these checks to check if "i" is a valid array index before using
> it. This prevents a potential off by one read access.
>
> Fixes: d6e290837e50 ("tee: add Qualcomm TEE driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> drivers/tee/qcomtee/call.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
>
> diff --git a/drivers/tee/qcomtee/call.c b/drivers/tee/qcomtee/call.c
> index cc17a48d0ab7..ac134452cc9c 100644
> --- a/drivers/tee/qcomtee/call.c
> +++ b/drivers/tee/qcomtee/call.c
> @@ -308,7 +308,7 @@ static int qcomtee_params_from_args(struct tee_param *params,
> }
>
> /* Release any IO and OO objects not processed. */
> - for (; u[i].type && i < num_params; i++) {
> + for (; i < num_params && u[i].type; i++) {
> if (u[i].type == QCOMTEE_ARG_TYPE_OO ||
> u[i].type == QCOMTEE_ARG_TYPE_IO)
> qcomtee_object_put(u[i].o);
> --
> 2.51.0
>
>
next prev parent reply other threads:[~2025-09-19 5:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 9:50 [PATCH next] tee: qcom: prevent potential off by one read Dan Carpenter
2025-09-18 9:50 ` Dan Carpenter
2025-09-19 5:21 ` Sumit Garg [this message]
2025-09-19 5:21 ` Sumit Garg via OP-TEE
2025-09-19 7:59 ` Jens Wiklander
2025-09-23 22:48 ` Amirreza Zarrabi
2025-09-23 22:48 ` Amirreza Zarrabi via OP-TEE
2025-09-23 22:58 ` Amirreza Zarrabi
2025-09-23 22:58 ` Amirreza Zarrabi via OP-TEE
2025-09-24 7:35 ` Dan Carpenter
2025-09-24 7:35 ` Dan Carpenter
2025-09-24 9:21 ` Jens Wiklander
2025-09-24 9:56 ` Dan Carpenter
2025-09-25 1:46 ` Amirreza Zarrabi
2025-09-25 1:46 ` Amirreza Zarrabi via OP-TEE
2025-09-24 7:32 ` Dan Carpenter
2025-09-24 7:32 ` Dan Carpenter
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=aMzoPc67ws5NMpKS@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=dan.carpenter@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.