|
Message-ID: <20170407015819.djxqzd2e5i3dd2dt@jeyu> Date: Thu, 6 Apr 2017 18:58:19 -0700 From: Jessica Yu <jeyu@...hat.com> To: Eddie Kovsky <ewk@...ovsky.org> Cc: rusty@...tcorp.com.au, keescook@...omium.org, linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com Subject: Re: [PATCH v5 1/2] module: verify address is read-only +++ 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@...omium.org> >Signed-off-by: Eddie Kovsky <ewk@...ovsky.org> Acked-by: Jessica Yu <jeyu@...hat.com>
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.