From: Vikash Garodia <quic_vgarodia@quicinc.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tomasz Figa <tfiga@chromium.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Cc: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<linux-media@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] media: venus: hfi: add a check to handle OOB in sfr region
Date: Thu, 20 Feb 2025 21:25:53 +0530 [thread overview]
Message-ID: <b1721d46-ffbf-e21c-ce18-e96e3e8ee35f@quicinc.com> (raw)
In-Reply-To: <e794c047-ab0e-4589-a1d2-0f73b813eacc@xs4all.nl>
On 2/20/2025 8:53 PM, Hans Verkuil wrote:
> On 2/7/25 09:24, Vikash Garodia wrote:
>> sfr->buf_size is in shared memory and can be modified by malicious user.
>> OOB write is possible when the size is made higher than actual sfr data
>> buffer. Cap the size to allocated size for such cases.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: d96d3f30c0f2 ("[media] media: venus: hfi: add Venus HFI files")
>> Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>> Signed-off-by: Vikash Garodia <quic_vgarodia@quicinc.com>
>> ---
>> drivers/media/platform/qcom/venus/hfi_venus.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/media/platform/qcom/venus/hfi_venus.c b/drivers/media/platform/qcom/venus/hfi_venus.c
>> index 6b615270c5dae470c6fad408c9b5bc037883e56e..c3113420d266e61fcab44688580288d7408b50f4 100644
>> --- a/drivers/media/platform/qcom/venus/hfi_venus.c
>> +++ b/drivers/media/platform/qcom/venus/hfi_venus.c
>> @@ -1041,18 +1041,23 @@ static void venus_sfr_print(struct venus_hfi_device *hdev)
>> {
>> struct device *dev = hdev->core->dev;
>> struct hfi_sfr *sfr = hdev->sfr.kva;
>> + u32 size;
>> void *p;
>>
>> if (!sfr)
>> return;
>>
>> - p = memchr(sfr->data, '\0', sfr->buf_size);
>> + size = sfr->buf_size;
>
> If this is ever 0...
>
>> + if (size > ALIGNED_SFR_SIZE)
>> + size = ALIGNED_SFR_SIZE;
>> +
>> + p = memchr(sfr->data, '\0', size);
>> /*
>> * SFR isn't guaranteed to be NULL terminated since SYS_ERROR indicates
>> * that Venus is in the process of crashing.
>> */
>> if (!p)
>> - sfr->data[sfr->buf_size - 1] = '\0';
>> + sfr->data[size - 1] = '\0';
>
> ...then this will overwrite memory. It probably can't be 0, but a check or perhaps
> just a comment might be good. It looks a bit scary.
Thats correct, it would not be 0 as its a prefixed one [1]. I can put up a
comment here.
[1]
https://elixir.bootlin.com/linux/v6.14-rc3/source/drivers/media/platform/qcom/venus/hfi_venus.c#L836
>
> Regards,
>
> Hans
>
>>
>> dev_err_ratelimited(dev, "SFR message from FW: %s\n", sfr->data);
>> }
>>
Regards,
Vikash
next prev parent reply other threads:[~2025-02-20 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 8:24 [PATCH v4 0/4] Venus driver fixes to avoid possible OOB accesses Vikash Garodia
2025-02-07 8:24 ` [PATCH v4 1/4] media: venus: hfi_parser: add check to avoid out of bound access Vikash Garodia
2025-02-20 15:16 ` Hans Verkuil
2025-02-20 15:25 ` Vikash Garodia
2025-02-07 8:24 ` [PATCH v4 2/4] media: venus: hfi_parser: refactor hfi packet parsing logic Vikash Garodia
2025-02-12 0:23 ` Bryan O'Donoghue
2025-02-20 15:20 ` Hans Verkuil
2025-02-20 15:38 ` Vikash Garodia
2025-02-20 15:42 ` Hans Verkuil
2025-02-20 15:47 ` Vikash Garodia
2025-02-07 8:24 ` [PATCH v4 3/4] media: venus: hfi: add check to handle incorrect queue size Vikash Garodia
2025-02-07 8:24 ` [PATCH v4 4/4] media: venus: hfi: add a check to handle OOB in sfr region Vikash Garodia
2025-02-20 15:23 ` Hans Verkuil
2025-02-20 15:55 ` Vikash Garodia [this message]
2025-02-21 3:55 ` Tomasz Figa
2025-02-21 16:25 ` Vikash Garodia
2025-02-12 0:23 ` [PATCH v4 0/4] Venus driver fixes to avoid possible OOB accesses Bryan O'Donoghue
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=b1721d46-ffbf-e21c-ce18-e96e3e8ee35f@quicinc.com \
--to=quic_vgarodia@quicinc.com \
--cc=bryan.odonoghue@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stanimir.k.varbanov@gmail.com \
--cc=stanimir.varbanov@linaro.org \
--cc=tfiga@chromium.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