mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Albert Esteve <aesteve@redhat.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sarannya S <sarannya.s@oss.qualcomm.com>,
	Pranav Mahesh Phansalkar <pranav.phansalkar@oss.qualcomm.com>,
	Sudeepgoud Patil <sudeep.patil@oss.qualcomm.com>
Subject: Re: [PATCH v4 2/4] soc: qcom: smem: validate private entry list walks
Date: Wed, 28 Oct 2026 09:29:48 +0100	[thread overview]
Message-ID: <auGyfKTc9QnREUr3@aesteve-thinkpadp1gen8.rmtes.csb> (raw)
In-Reply-To: <abf21903-16ee-4d3c-8bd4-84ac2c4623f8@oss.qualcomm.com>

On Tue, Oct 27, 2026 at 01:45:26PM +0100, Konrad Dybcio wrote:
> On 10/22/26 11:47 AM, Albert Esteve wrote:
> > From: Sarannya S <sarannya.s@oss.qualcomm.com>
> > 
> > When walking private entries, use the uncached/cached free offsets as
> > the list bounds, require room for a header before dereferencing, and
> > reject a next pointer that does not advance.
> > 
> > Skip the cached list when the cached free offset is at the partition
> > end.
> > 
> > Signed-off-by: Sarannya S <sarannya.s@oss.qualcomm.com>
> > Signed-off-by: Pranav Mahesh Phansalkar <pranav.phansalkar@oss.qualcomm.com>
> > Signed-off-by: Sudeepgoud Patil <sudeep.patil@oss.qualcomm.com>
> > Signed-off-by: Albert Esteve <aesteve@redhat.com>
> > ---
> >  drivers/soc/qcom/smem.c | 52 ++++++++++++++++++++++++++++++++++++-------------
> >  1 file changed, 38 insertions(+), 14 deletions(-)
> > 
> > diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
> > index 36a4a10f3aec..a6732832e2c5 100644
> > --- a/drivers/soc/qcom/smem.c
> > +++ b/drivers/soc/qcom/smem.c
> > @@ -422,6 +422,7 @@ static int qcom_smem_alloc_private(struct qcom_smem *smem,
> >  				   size_t size)
> >  {
> >  	struct smem_private_entry *hdr, *end;
> > +	struct smem_private_entry *next_hdr;
> >  	struct smem_partition_header *phdr;
> >  	size_t alloc_size;
> >  	void *cached;
> > @@ -434,19 +435,25 @@ static int qcom_smem_alloc_private(struct qcom_smem *smem,
> >  	end = phdr_to_last_uncached_entry(phdr);
> >  	cached = phdr_to_last_cached_entry(phdr);
> >  
> > -	if (WARN_ON((void *)end > p_end || cached > p_end))
> > +	if (WARN_ON(!IN_PARTITION_RANGE(end, 0, phdr, cached) ||
> > +			cached > p_end))
> 
> nit: i wouldn't break this line, and otherwise the next line should
> start below where the first condition starts

Right. The statement fits in one line so will do that.

> 
> [...]
> 
> > -	if (WARN_ON((void *)hdr > p_end))
> > +	if (WARN_ON((void *)hdr > (void *)end))
> 
> LLM noticed that before this patch, we risk overrunning end, but with
> this patch, we now risk a corrupted/malicious partition ending before
> 'end'. A valid walk always lands exactly on `end`, so the fix is:
> 
> if (WARN_ON(hdr != end))
>     return -EINVAL;

I see, makes sense. Will do as suggested.

> 
> 
> Otherwise my clanker is reasonably happy and I see nothing wrong
> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Thanks!

> 
> Konrad


  reply	other threads:[~2026-10-28  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22  9:47 [PATCH v4 0/4] Add automotive SMEM hardening for Qualcomm platforms Albert Esteve
2026-10-22  9:47 ` [PATCH v4 1/4] soc: qcom: smem: add IN_PARTITION_RANGE helper Albert Esteve
2026-10-27 12:18   ` Konrad Dybcio
2026-10-22  9:47 ` [PATCH v4 2/4] soc: qcom: smem: validate private entry list walks Albert Esteve
2026-10-27 12:45   ` Konrad Dybcio
2026-10-28  8:29     ` Albert Esteve [this message]
2026-10-22  9:47 ` [PATCH v4 3/4] soc: qcom: smem: validate private item payloads Albert Esteve
2026-10-27 12:58   ` Konrad Dybcio
2026-10-22  9:47 ` [PATCH v4 4/4] soc: qcom: smem: ignore multi remote host partitions Albert Esteve

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=auGyfKTc9QnREUr3@aesteve-thinkpadp1gen8.rmtes.csb \
    --to=aesteve@redhat.com \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranav.phansalkar@oss.qualcomm.com \
    --cc=sarannya.s@oss.qualcomm.com \
    --cc=sudeep.patil@oss.qualcomm.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®