[PATCH 05/38] Annotate hardware config module parameters in drivers/char/

Greg KH gregkh at linuxfoundation.org
Sat Apr 8 15:23:23 UTC 2017


On Wed, Apr 05, 2017 at 05:57:30PM +0100, David Howells 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 drivers/char/.
> 
> Suggested-by: Alan Cox <gnomes at lxorguk.ukuu.org.uk>
> Signed-off-by: David Howells <dhowells at redhat.com>
> cc: Arnd Bergmann <arnd at arndb.de>
> cc: Greg Kroah-Hartman <gregkh at linuxfoundation.org>

Acked-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



More information about the Linux-security-module-archive mailing list