mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: jeyu@kernel.org
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: [PATCH] x86/module: Detect corrupt relocations against nonzero data
Date: Thu, 2 Nov 2017 21:19:42 -0500	[thread overview]
Message-ID: <20171103021942.nfxsdp43cziaoiow@treble> (raw)
In-Reply-To: <3999d59e87ad73d4030e98bd90a6ffc00bc054d2.1509659611.git.jpoimboe@redhat.com>

On Thu, Nov 02, 2017 at 04:57:11PM -0500, Josh Poimboeuf wrote:
> There have been some cases where external tooling (e.g., kpatch-build)
> creates a corrupt relocation which targets the wrong address.  This is a
> silent failure which can corrupt memory in unexpected places.
> 
> On x86, the bytes of data being overwritten by relocations are always
> initialized to zero beforehand.  Use that knowledge to add sanity checks
> to detect such cases before they corrupt memory.
> 
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> ---
>  arch/x86/kernel/module.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/arch/x86/kernel/module.c b/arch/x86/kernel/module.c
> index 62e7d70aadd5..a69b12617820 100644
> --- a/arch/x86/kernel/module.c
> +++ b/arch/x86/kernel/module.c
> @@ -172,19 +172,27 @@ int apply_relocate_add(Elf64_Shdr *sechdrs,
>  		case R_X86_64_NONE:
>  			break;
>  		case R_X86_64_64:
> +			if (*(u64 *)loc != 0)
> +				goto nonzero;
>  			*(u64 *)loc = val;
>  			break;
>  		case R_X86_64_32:
> +			if (*(u32 *)loc != 0)
> +				goto nonzero;
>  			*(u32 *)loc = val;
>  			if (val != *(u32 *)loc)
>  				goto overflow;
>  			break;
>  		case R_X86_64_32S:
> +			if (*(s32 *)loc != 0)
> +				goto nonzero;
>  			*(s32 *)loc = val;
>  			if ((s64)val != *(s32 *)loc)
>  				goto overflow;
>  			break;
>  		case R_X86_64_PC32:
> +			if (*(u64 *)loc != 0)
> +				goto nonzero;
>  			val -= (u64)loc;
>  			*(u32 *)loc = val;

NACK - this last bit is obviously a bug, not sure how it passed my
testing without module load failures...

-- 
Josh

  reply	other threads:[~2017-11-03  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 21:57 Josh Poimboeuf
2017-11-03  2:19 ` Josh Poimboeuf [this message]
2017-11-03 10:22   ` Jessica Yu

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=20171103021942.nfxsdp43cziaoiow@treble \
    --to=jpoimboe@redhat.com \
    --cc=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.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

all inboxes | Powered by JetHome®