linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Kees Cook <keescook@chromium.org>
Cc: "linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Evgeniy Didin <Evgeniy.Didin@synopsys.com>
Subject: Re: [PATCH] ARC: fix CONFIG_HARDENED_USERCOPY
Date: Thu, 10 Jun 2021 18:56:48 +0000	[thread overview]
Message-ID: <53daee07-9c5b-9cf9-f08a-524afaee762a@synopsys.com> (raw)
In-Reply-To: <202106101001.C736237@keescook>

On 6/10/21 10:02 AM, Kees Cook wrote:
> On Wed, Jun 09, 2021 at 03:12:11PM -0700, Vineet Gupta wrote:
>> Currently enabling this triggers a warning
>>
>> | usercopy: Kernel memory overwrite attempt detected to kernel text (offset 155633, size 11)!
>> | usercopy: BUG: failure at mm/usercopy.c:99/usercopy_abort()!
>> |
>> |gcc generated __builtin_trap
>> |Path: /bin/busybox
>> |CPU: 0 PID: 84 Comm: init Not tainted 5.4.22
>> |
>> |[ECR ]: 0x00090005 => gcc generated __builtin_trap
>> |[EFA ]: 0x9024fcaa
>> |[BLINK ]: usercopy_abort+0x8a/0x8c
>> |[ERET ]: memfd_fcntl+0x0/0x470
>> |[STAT32]: 0x80080802 : IE K
>> |BTA: 0x901ba38c SP: 0xbe161ecc FP: 0xbf9fe950
>> |LPS: 0x90677408 LPE: 0x9067740c LPC: 0x00000000
>> |r00: 0x0000003c r01: 0xbf0ed280 r02: 0x00000000
>> |r03: 0xbe15fa30 r04: 0x00d2803e r05: 0x00000000
>> |r06: 0x675d7000 r07: 0x00000000 r08: 0x675d9c00
>> |r09: 0x00000000 r10: 0x0000035c r11: 0x61206572
>> |r12: 0x9024fcaa r13: 0x0000000b r14: 0x0000000b
>> |r15: 0x00000000 r16: 0x90169ffc r17: 0x90168000
>> |r18: 0x00000000 r19: 0xbf092010 r20: 0x00000001
>> |r21: 0x00000011 r22: 0x5ffffff1 r23: 0x90169ff1
>> |r24: 0xbe196c00 r25: 0xbf0ed280
>> |
>> |Stack Trace:
>> | memfd_fcntl+0x0/0x470
>> | usercopy_abort+0x8a/0x8c
>> | __check_object_size+0x10e/0x138
>> | copy_strings+0x1f4/0x38c
>> | __do_execve_file+0x352/0x848
>> | EV_Trap+0xcc/0xd0
> What was the root cause here? Was it that the init section gets freed
> and reused for kmalloc?

Right. ARC _stext was encompassing the init section (to cover the init 
code) so when init gets freed and used by kmalloc, 
check_kernel_text_object() trips as it thinks the allocated pointer is 
in kernel .text. Actually I should have added this to changelog.

Thx,
-Vineet


  reply	other threads:[~2021-06-10 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 22:12 [PATCH] ARC: fix CONFIG_HARDENED_USERCOPY Vineet Gupta
2021-06-10 17:02 ` Kees Cook
2021-06-10 18:56   ` Vineet Gupta [this message]
2021-06-10 23:56     ` Kees Cook
2021-06-11  0:29       ` Vineet Gupta

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=53daee07-9c5b-9cf9-f08a-524afaee762a@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Evgeniy.Didin@synopsys.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.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;
as well as URLs for NNTP newsgroup(s).