linux-kernel - Re: [PATCH 34/38] Annotate hardware config module parameters in fs/pstore/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGXu5j+1qtNNXz8XSnifT7uy97u-Hox76bBHN3H-VsmVB_VwKg@mail.gmail.com>
Date:   Wed, 5 Apr 2017 10:04:15 -0700
From:   Kees Cook <keescook@...omium.org>
To:     David Howells <dhowells@...hat.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        "gnomes@...rguk.ukuu.org.uk" <gnomes@...rguk.ukuu.org.uk>,
        Tony Luck <tony.luck@...el.com>,
        Greg KH <gregkh@...uxfoundation.org>,
        Anton Vorontsov <anton@...msg.org>,
        linux-security-module <linux-security-module@...r.kernel.org>,
        keyrings@...r.kernel.org, Colin Cross <ccross@...roid.com>
Subject: Re: [PATCH 34/38] Annotate hardware config module parameters in fs/pstore/

On Wed, Apr 5, 2017 at 10:01 AM, David Howells <dhowells@...hat.com> wrote:
> When the kernel is running in secure boot mode, we lock down the kernel to
> prevent userspace from modifying the running kernel image.  Whilst this
> includes prohibiting access to things like /dev/mem, it must also prevent
> access by means of configuring driver modules in such a way as to cause a
> device to access or modify the kernel image.
>
> To this end, annotate module_param* statements that refer to hardware
> configuration and indicate for future reference what type of parameter they
> specify.  The parameter parser in the core sees this information and can
> skip such parameters with an error message if the kernel is locked down.
> The module initialisation then runs as normal, but just sees whatever the
> default values for those parameters is.
>
> Note that we do still need to do the module initialisation because some
> drivers have viable defaults set in case parameters aren't specified and
> some drivers support automatic configuration (e.g. PNP or PCI) in addition
> to manually coded parameters.
>
> This patch annotates drivers in fs/pstore/.
>
> Suggested-by: Alan Cox <gnomes@...rguk.ukuu.org.uk>
> Signed-off-by: David Howells <dhowells@...hat.com>
> cc: Anton Vorontsov <anton@...msg.org>
> cc: Colin Cross <ccross@...roid.com>
> cc: Kees Cook <keescook@...omium.org>
> cc: Tony Luck <tony.luck@...el.com>

Acked-by: Kees Cook <keescook@...omium.org>

-Kees

> ---
>
>  fs/pstore/ram.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
> index 11f918d34b1e..cce1d38417ca 100644
> --- a/fs/pstore/ram.c
> +++ b/fs/pstore/ram.c
> @@ -58,7 +58,7 @@ module_param_named(pmsg_size, ramoops_pmsg_size, ulong, 0400);
>  MODULE_PARM_DESC(pmsg_size, "size of user space message log");
>
>  static unsigned long long mem_address;
> -module_param(mem_address, ullong, 0400);
> +module_param_hw(mem_address, ullong, other, 0400);
>  MODULE_PARM_DESC(mem_address,
>                 "start of reserved RAM used to store oops/panic logs");
>
>



-- 
Kees Cook
Pixel Security