From: Auditya Bhattaram <quic_audityab@quicinc.com>
To: Mukesh Ojha <quic_mojha@quicinc.com>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] soc: qcom: mdt_loader: Add Upperbounds check for program header access
Date: Thu, 8 Feb 2024 17:14:47 +0530 [thread overview]
Message-ID: <c4a6500d-7fdd-4e62-bc96-bd2e164f3bc4@quicinc.com> (raw)
In-Reply-To: <9773d189-c896-d5c5-804c-e086c24987b4@quicinc.com>
On 2/2/2024 1:34 PM, Mukesh Ojha wrote:
>
> This should be v2., first time patches is always counted as v1
>
> On 2/2/2024 12:09 PM, Auditya Bhattaram wrote:
>> hash_index is evaluated by looping phdrs till QCOM_MDT_TYPE_HASH
>> is found. Add an upperbound check to phdrs to access within elf size.
>>
>> Signed-off-by: Auditya Bhattaram <quic_audityab@quicinc.com> > ---
>> Added error prints for Invalid access.
>> Link for previous discussion
>> https://lore.kernel.org/linux-arm-msm/5d7a3b97-d840-4863-91a0-32c1d8e7532f@linaro.org/T/#t
>
> Would be better if you take reference from other patches,
>
> Like above can be done as,
>
> Changes in v2:
> - ...
> - ,,,
>> ---
>> drivers/soc/qcom/mdt_loader.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/soc/qcom/mdt_loader.c
>> b/drivers/soc/qcom/mdt_loader.c
>> index 6f177e46fa0f..61e2377cc5c3 100644
>> --- a/drivers/soc/qcom/mdt_loader.c
>> +++ b/drivers/soc/qcom/mdt_loader.c
>> @@ -145,6 +145,11 @@ void *qcom_mdt_read_metadata(const struct
>> firmware *fw, size_t *data_len,
>> if (phdrs[0].p_type == PT_LOAD)
>> return ERR_PTR(-EINVAL);
>>
>> + if (((size_t)(phdrs + ehdr->e_phnum)) > ((size_t)ehdr + fw->size)) {
>> + dev_err(dev, "Invalid phdrs access: %s\n", fw_name);
>> + return ERR_PTR(-EINVAL);
>> + }
>> +
>
> Should this not be marked for stable kernel ? as without this it could
> be accessing beyond fw_size for uncertain scenario.
>
> -Mukesh
Yes This should be marked for stable.
>
>> for (i = 1; i < ehdr->e_phnum; i++) {
>> if ((phdrs[i].p_flags & QCOM_MDT_TYPE_MASK) ==
>> QCOM_MDT_TYPE_HASH) {
>> hash_segment = i;
>> --
>> 2.17.1
>>
>>
prev parent reply other threads:[~2024-02-08 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 6:39 [PATCH v1] soc: qcom: mdt_loader: Add Upperbounds check for program header access Auditya Bhattaram
2024-02-02 8:04 ` Mukesh Ojha
2024-02-08 11:44 ` Auditya Bhattaram [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=c4a6500d-7fdd-4e62-bc96-bd2e164f3bc4@quicinc.com \
--to=quic_audityab@quicinc.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.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