From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vedang Nagar <quic_vnagar@quicinc.com>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] media: venus: fix OOB access issue while reading sequence changed events
Date: Tue, 4 Mar 2025 13:35:40 +0000 [thread overview]
Message-ID: <664809e5-c027-4d0e-a604-d9fdf4b1f2da@linaro.org> (raw)
In-Reply-To: <20250215-venus-security-fixes-v2-2-cfc7e4b87168@quicinc.com>
On 15/02/2025 17:19, Vedang Nagar wrote:
> num_properties_changed is being read from the message queue but is
> not validated. Value can be corrupted from the firmware leading to
> OOB read access issues. Add fix to read the size of the packets as
> well and crosscheck before reading from the packet.
>
> Signed-off-by: Vedang Nagar <quic_vnagar@quicinc.com>
> ---
> drivers/media/platform/qcom/venus/hfi_msgs.c | 72 ++++++++++++++++++++++++----
> 1 file changed, 62 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/media/platform/qcom/venus/hfi_msgs.c b/drivers/media/platform/qcom/venus/hfi_msgs.c
> index 0a041b4db9efc549621de07dd13b4a3a37a70d11..2ad60a3fbfe0286de09a44664fc3b30259aa0368 100644
> --- a/drivers/media/platform/qcom/venus/hfi_msgs.c
> +++ b/drivers/media/platform/qcom/venus/hfi_msgs.c
> @@ -19,6 +19,16 @@
> #define VER_STR_SZ 128
> #define SMEM_IMG_OFFSET_VENUS (14 * 128)
>
> +static inline int increment_data_ptr(u8 *data_ptr, u32 *rem_bytes)
> +{
> + if (*rem_bytes < sizeof(u32))
> + return -EINVAL;
> + data_ptr += sizeof(u32);
> + *rem_bytes -= sizeof(u32);
> +
> + return 0;
> +}
> +
> static void event_seq_changed(struct venus_core *core, struct venus_inst *inst,
> struct hfi_msg_event_notify_pkt *pkt)
> {
> @@ -33,8 +43,8 @@ static void event_seq_changed(struct venus_core *core, struct venus_inst *inst,
> struct hfi_buffer_requirements *bufreq;
> struct hfi_extradata_input_crop *crop;
> struct hfi_dpb_counts *dpb_count;
> + u32 ptype, rem_bytes;
> u8 *data_ptr;
> - u32 ptype;
>
> inst->error = HFI_ERR_NONE;
>
> @@ -56,66 +66,108 @@ static void event_seq_changed(struct venus_core *core, struct venus_inst *inst,
> }
>
> data_ptr = (u8 *)&pkt->ext_event_data[0];
> + rem_bytes = pkt->shdr.hdr.size - sizeof(*pkt);
> + if (rem_bytes - 4 < 0) {
> + inst->error = HFI_ERR_SESSION_INSUFFICIENT_RESOURCES;
> + goto done;
> + }
This doesn't make sense.
u32 rem_bytes;
if (rem_bytes - 4 < 0)
> +
> do {
> ptype = *((u32 *)data_ptr);
> switch (ptype) {
> case HFI_PROPERTY_PARAM_FRAME_SIZE:
> - data_ptr += sizeof(u32);
> + if (increment_data_ptr(data_ptr, &rem_bytes))
> + break;
> + if (rem_bytes < sizeof(struct hfi_framesize))
> + break;
In every case you are return -EINVAL but not setting
inst->error = HFI_ERR_SESSION_INSUFFICIENT_RESOURCES;
surely that is a natural and logical outcome of running out of buffer
and a fact you'd want to communicate outside of the driver, rather than
silent failing in this switch ?
---
bod
next prev parent reply other threads:[~2025-03-04 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 17:19 [PATCH v2 0/2] venus driver fixes to avoid possible OOB read access Vedang Nagar
2025-02-15 17:19 ` [PATCH v2 1/2] media: venus: fix OOB read issue due to double read Vedang Nagar
2025-03-04 13:45 ` Bryan O'Donoghue
2025-05-13 13:13 ` Dikshita Agarwal
2025-02-15 17:19 ` [PATCH v2 2/2] media: venus: fix OOB access issue while reading sequence changed events Vedang Nagar
2025-03-04 13:35 ` Bryan O'Donoghue [this message]
2025-05-13 7:02 ` Dikshita Agarwal
2025-05-13 13:00 ` Vikash Garodia
2025-02-16 16:03 ` [PATCH v2 0/2] venus driver fixes to avoid possible OOB read access Bryan O'Donoghue
2025-03-02 11:58 ` Vedang Nagar
2025-03-02 15:56 ` Bryan O'Donoghue
2025-03-03 13:12 ` Vikash Garodia
2025-03-03 14:56 ` Bryan O'Donoghue
2025-03-03 15:01 ` Vikash Garodia
2025-03-04 13:30 ` 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=664809e5-c027-4d0e-a604-d9fdf4b1f2da@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vgarodia@quicinc.com \
--cc=quic_vnagar@quicinc.com \
--cc=stanimir.k.varbanov@gmail.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