Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Kees Cook <keescook@chromium.org>,
	peterz@infradead.org
Subject: Re: [PATCH] lkdtm: cfi: add test for HW landing pad CFI
Date: Thu, 14 Jul 2022 12:31:54 +0100	[thread overview]
Message-ID: <Ys/+qghGmH4kK4DN@FVFF77S0Q05N> (raw)
In-Reply-To: <Ys7vRTThFVNz7moO@sirena.org.uk>

On Wed, Jul 13, 2022 at 05:13:57PM +0100, Mark Brown wrote:
> On Wed, Jul 13, 2022 at 04:18:15PM +0100, Mark Rutland wrote:
> > Some architectures have coarse-grained HW CFI schemes where indirect
> > branches must target a "landing pad" instruction (e.g. BTI on arm64,
> > ENDBR on x86). These prevent gadgetization of arbitrary portions of
> > functions.
> 
> > Add a test which checks these work as expected.
> 
> > For example, on arm64 HW with BTI this should result in a BTI exception
> > being taken:
> 
> > +/*
> > + * This tries to call an indirect function with an address which is not a
> > + * function entry point. This should be caught by architectures with "landing
> > + * pad" instructions (e.g. BTI on arm64, or ENDBR on x86).
> > + */
> > +static void lkdtm_CFI_FORWARD_LANDING_PAD(void)
> > +{
> > +	void (*func)(int *);
> > +
> > +	func = (void *)((unsigned long)lkdtm_increment_void + 4);
> > +
> > +	pr_info("Calling gadget address ...\n");
> > +	func(&called_count);
> > +
> > +	pr_err("FAIL: survived gadget function call!\n");
> > +}
> 
> Incrementing the address by 4 here is the right number for arm64 and it
> looks like it's also right for the x86_64 ENDBR64 instruction but are we
> guaranteed that it'll do the right thing for other architectures,
> especially those with variable length instructions - couldn't we just
> get an illegal instruction exception due to ending up pointing at
> something that isn't the start of an instruction even if CFI isn't
> active?
> 
> Not sure that worrying about that at this point isn't making perfect the
> enemy of good though, it could be dealt with later.  Perhaps just put
> the offset behind a #define to make it a tiny bit more discoverable?

How about I just add a comment for now? e.g.

	/*
	 * Skip past a landing pad instruction.
	 * On arm64 all instructions are 4-byte aligned, and x86's ENDBR is 4
	 * bytes.
	 */

Thanks,
Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-07-14 11:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 15:18 [PATCH] lkdtm: cfi: add test for HW landing pad CFI Mark Rutland
2022-07-13 16:13 ` Mark Brown
2022-07-14 11:31   ` Mark Rutland [this message]
2022-07-14 12:06     ` Mark Brown

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=Ys/+qghGmH4kK4DN@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=broonie@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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