Re: [PATCH v5 next 2/5] modules:capabilities: add cap_kernel_module_request() permission check

From
Luis R. Rodriguez <mcgrof@kernel.org>
Date
2017-11-30 02:06:04
Also in
linux-security-module, lkml
Reply to
Djalal Harouni, 2017-11-27
On Mon, Nov 27, 2017 at 06:18:35PM +0100, Djalal Harouni wrote:
quoted hunk ↗ jump to hunk
+/* Determine whether a module auto-load operation is permitted. */
+int may_autoload_module(char *kmod_name, int required_cap,
+			const char *kmod_prefix);
+
While we are reviewing a general LSM for this, it has me wondering if an LSM or
userspace feed info may every want to use other possible context we could add for
free to make a determination.

For instance since all request_module() calls are in header files, we could 
for add for free THIS_MODULE as context to may_autoload_module() as well, so
struct module. The LSM could in theory then also help ensure only specific
modules are allowed to request a module load. Perhaps userspace could say
only built-in code could request certain modules.

Just a thought.

  Luis
Thread (49 messages) 49 messages, 11 authors, last reply 2017-11-30
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help