Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1619090

Re: [PATCH v5 1/2] module: verify address is read-only

From Kees Cook <keescook@chromium.org>
Newsgroups linux.kernel
Subject Re: [PATCH v5 1/2] module: verify address is read-only
Date 2017-04-07 22:50 +0200
Message-ID <ttIZr-4bj-7@gated-at.bofh.it> (permalink)
References <tt6r8-36F-1@gated-at.bofh.it> <tt6r8-36F-3@gated-at.bofh.it> <ttrlT-vw-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Apr 6, 2017 at 6:58 PM, Jessica Yu <jeyu@redhat.com> wrote:
> +++ Eddie Kovsky [05/04/17 21:35 -0600]:
>>
>> Implement a mechanism to check if a module's address is in
>> the rodata or ro_after_init sections. It mimics the existing functions
>> that test if an address is inside a module's text section.
>>
>> Functions that take a module as an argument will be able to verify that
>> the
>> module address is in a read-only section. The idea is to prevent
>> structures
>> (including modules) that are not read-only from being passed to functions.
>>
>> This implements the first half of a suggestion made by Kees Cook for
>> the Kernel Self Protection Project:
>>
>>    - provide mechanism to check for ro_after_init memory areas, and
>>      reject structures not marked ro_after_init in vmbus_register()
>>
>> Suggested-by: Kees Cook <keescook@chromium.org>
>> Signed-off-by: Eddie Kovsky <ewk@edkovsky.org>
>
>
> Acked-by: Jessica Yu <jeyu@redhat.com>

Thanks! I'll either get these into my kspp tree or ask akpm to carry
these since they depend on the renaming in his tree already.

-Kees

-- 
Kees Cook
Pixel Security

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v5 0/2] provide check for ro_after_init memory sections Eddie Kovsky <ewk@edkovsky.org> - 2017-04-06 05:40 +0200
  [PATCH v5 1/2] module: verify address is read-only Eddie Kovsky <ewk@edkovsky.org> - 2017-04-06 05:40 +0200
    Re: [PATCH v5 1/2] module: verify address is read-only Jessica Yu <jeyu@redhat.com> - 2017-04-07 04:00 +0200
      Re: [PATCH v5 1/2] module: verify address is read-only Kees Cook <keescook@chromium.org> - 2017-04-07 22:50 +0200
  [PATCH v5 2/2] extable: verify address is read-only Eddie Kovsky <ewk@edkovsky.org> - 2017-04-06 05:40 +0200
    Re: [PATCH v5 2/2] extable: verify address is read-only kbuild test robot <lkp@intel.com> - 2017-04-06 19:50 +0200
      Re: [PATCH v5 2/2] extable: verify address is read-only Eddie Kovsky <ewk@edkovsky.org> - 2017-04-07 21:30 +0200
        Re: [PATCH v5 2/2] extable: verify address is read-only Kees Cook <keescook@chromium.org> - 2017-04-07 22:50 +0200
  Re: [PATCH v5 0/2] provide check for ro_after_init memory sections Kees Cook <keescook@chromium.org> - 2017-04-08 00:00 +0200
    Re: [PATCH v5 0/2] provide check for ro_after_init memory sections Andrew Morton <akpm@linux-foundation.org> - 2017-04-08 00:20 +0200
      Re: [PATCH v5 0/2] provide check for ro_after_init memory sections Kees Cook <keescook@chromium.org> - 2017-04-08 00:20 +0200
        Re: [PATCH v5 0/2] provide check for ro_after_init memory sections Andrew Morton <akpm@linux-foundation.org> - 2017-04-08 00:30 +0200
          Re: [PATCH v5 0/2] provide check for ro_after_init memory sections Kees Cook <keescook@chromium.org> - 2017-04-08 00:50 +0200

csiph-web