From: Philippe Schenker <dev@pschenker.ch>
To: Andrew Davis <afd@ti.com>, u-boot@lists.denx.de
Cc: stefan@embear.ch, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v1 4/6] mach-k3: security: Propagate verified image addr
Date: Thu, 06 Nov 2025 13:33:35 +0100 [thread overview]
Message-ID: <3fbc597ddb07590d36498ca7993df524c002e450.camel@pschenker.ch> (raw)
In-Reply-To: <f499c3ea-72ce-4698-91d2-b10aa8c438bf@ti.com>
On Thu, 2025-10-23 at 09:24 -0500, Andrew Davis wrote:
> On 10/23/25 4:46 AM, Philippe Schenker wrote:
> > From: Philippe Schenker <philippe.schenker@impulsing.ch>
> >
> > The ti_secure_image_check() function may relocate the image during
> > authentication, updating image_addr to point to the verified
> > location.
> > The caller was not updated with this new address, causing it to
> > reference the original unverified location.
> >
> > Update p_image with the verified image address after authentication
> > to ensure subsequent operations use the correct location.
> >
> > Signed-off-by: Philippe Schenker <philippe.schenker@impulsing.ch>
> > ---
>
> Seems reasonable,
>
> Acked-by: Andrew Davis <afd@ti.com>
>
> BTW, did you actually run into an issue with having a binary moved
> by the authentication, or was this found some other way? Normally
> binaries don't move (but they can, so this is still valid).
Thanks for your acked-by's! Sorry forgot to answer and just now saw it
again. Yes I ran into an issue where I have a signed elf file. The step
of loading the elf file was failing because the pointer still pointing
to the signature.
Philippe
>
> >
> > arch/arm/mach-k3/security.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/arm/mach-k3/security.c b/arch/arm/mach-
> > k3/security.c
> > index 3468a370a455..9255505a7944 100644
> > --- a/arch/arm/mach-k3/security.c
> > +++ b/arch/arm/mach-k3/security.c
> > @@ -119,6 +119,8 @@ void ti_secure_image_post_process(void
> > **p_image, size_t *p_size)
> > */
> > *p_size = image_size;
> >
> > + *p_image = (void *)image_addr;
> > +
> > /*
> > * Output notification of successful authentication to re-assure
> > the
> > * user that the secure code is being processed as expected.
> > However
next prev parent reply other threads:[~2025-11-06 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 9:46 [PATCH v1 0/6] remoteproc: k3-r5: Build fixes and security improvements Philippe Schenker
2025-10-23 9:46 ` [PATCH v1 1/6] arm: dts: k3-am642-evm: Remove duplicate node Philippe Schenker
2025-10-23 9:46 ` [PATCH v1 2/6] remoteproc: k3-r5: cast size to size_t Philippe Schenker
2025-10-23 14:22 ` Andrew Davis
2025-10-23 9:46 ` [PATCH v1 3/6] soc: ti: pruss: Fix size ptr type in probe Philippe Schenker
2025-10-23 9:46 ` [PATCH v1 4/6] mach-k3: security: Propagate verified image addr Philippe Schenker
2025-10-23 14:24 ` Andrew Davis
2025-11-06 12:33 ` Philippe Schenker [this message]
2025-10-23 9:46 ` [PATCH v1 5/6] remoteproc: k3-r5: Use verified image address Philippe Schenker
2025-10-23 9:46 ` [PATCH v1 6/6] remoteproc: k3-r5: Implement is_running operation Philippe Schenker
2025-11-06 19:35 ` [PATCH v1 0/6] remoteproc: k3-r5: Build fixes and security improvements Tom Rini
2025-11-07 8:21 ` Philippe Schenker
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=3fbc597ddb07590d36498ca7993df524c002e450.camel@pschenker.ch \
--to=dev@pschenker.ch \
--cc=afd@ti.com \
--cc=stefan@embear.ch \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.