Skip to contentSkip to conversation

fw_lockdown: new micro LSM module to prevent loading unsigned firmware

RFC PATCH In review Mimi Zohar 2 participants 5 messages Nov 10, 2017

Subsystems (2)
lore
Share & tools
lore

Mimi Zohar

author
#0 lore raw

RFC PATCH 1/1 fw_lockdown: new micro LSM module to prevent loading unsigned firmware

Hi David,

If you are interested in preventing the loading of unsigned firmware, the patch below is straight forward. ?The patch has ONLY been tested with IMA-appraisal enabled, and works as intended - allowing only signed firmware to be loaded.

Mimi
---

If the kernel is locked down and IMA-appraisal is not enabled, prevent loading of unsigned firmware.

---
 security/Kconfig                   |  1 +
 security/Makefile                  |  2 ++
 security/fw_lockdown/Kconfig       |  6 +++++
 security/fw_lockdown/Makefile      |  3 +++
 security/fw_lockdown/fw_lockdown.c | 52 ++++++++++++++++++++++++++++++++++++++
 5 files changed, 64 insertions(+)
 create mode 100644 security/fw_lockdown/Kconfig
 create mode 100644 security/fw_lockdown/Makefile
 create mode 100644 security/fw_lockdown/fw_lockdown.c
security/Kconfig +1 -0
index a4fa8b826039..6e7e5888f823 100644
@@ -243,6 +243,7 @@ source security/tomoyo/Kconfig
 source security/apparmor/Kconfig
 source security/loadpin/Kconfig
 source security/yama/Kconfig
+source security/fw_lockdown/Kconfig
 
 source security/integrity/Kconfig
 
security/Makefile +2 -0
index 8c4a43e3d4e0..58852dee5e22 100644
@@ -9,6 +9,7 @@ subdir-$(CONFIG_SECURITY_TOMOYO)        += tomoyo
 subdir-$(CONFIG_SECURITY_APPARMOR)	+= apparmor
 subdir-$(CONFIG_SECURITY_YAMA)		+= yama
 subdir-$(CONFIG_SECURITY_LOADPIN)	+= loadpin
+subdir-$(CONFIG_SECURITY_FW_LOCKDOWN)	+= fw_lockdown
 
 # always enable default capabilities
 obj-y					+= commoncap.o
@@ -24,6 +25,7 @@ obj-$(CONFIG_SECURITY_TOMOYO)		+= tomoyo/
 obj-$(CONFIG_SECURITY_APPARMOR)		+= apparmor/
 obj-$(CONFIG_SECURITY_YAMA)		+= yama/
 obj-$(CONFIG_SECURITY_LOADPIN)		+= loadpin/
+obj-$(CONFIG_SECURITY_FW_LOCKDOWN)	+= fw_lockdown/
 obj-$(CONFIG_CGROUP_DEVICE)		+= device_cgroup.o
 
 # Object integrity file lists
security/fw_lockdown/Kconfig new file +6 -0
new file mode 100644
index 000000000000..cb7780f7c7f5
@@ -0,0 +1,6 @@
+config SECURITY_FW_LOCKDOWN
+	bool "Prevent loading unsigned firmware"
+	depends on SECURITY && CONFIG_LOCK_DOWN_KERNEL
+	default y
+	help
+	  Prevent loading unsigned firmware in lockdown mode,
security/fw_lockdown/Makefile new file +3 -0
new file mode 100644
index 000000000000..9798a396d4ef
@@ -0,0 +1,3 @@
+obj-$(CONFIG_SECURITY_FW_LOCKDOWN) += fw_lockdown.o
+
+fw_lockdown-y := fw_lockdown.o
security/fw_lockdown/fw_lockdown.c new file +52 -0

52 lines not on this page · raw message

Signature · 6 lines
2.7.4

--
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
#1 lore raw
Quoted 6 lines · Mimi Zohar

Hi David,

If you are interested in preventing the loading of unsigned firmware, the patch below is straight forward. �The patch has ONLY been tested with IMA-appraisal enabled, and works as intended - allowing only signed firmware to be loaded.

Very nice! This is the sort of thing that I mean by LSM'ifying fw access through a system policy.

We currently handle the LSM aspect for firmware through kernel_read_file_from_path() and so the kernel_read_file LSM hook, so why a new hook here?

Where does this plug in?

Quoted 133 lines

Mimi
---

If the kernel is locked down and IMA-appraisal is not enabled, prevent loading of unsigned firmware.

---
 security/Kconfig                   |  1 +
 security/Makefile                  |  2 ++
 security/fw_lockdown/Kconfig       |  6 +++++
 security/fw_lockdown/Makefile      |  3 +++
 security/fw_lockdown/fw_lockdown.c | 52 ++++++++++++++++++++++++++++++++++++++
 5 files changed, 64 insertions(+)
 create mode 100644 security/fw_lockdown/Kconfig
 create mode 100644 security/fw_lockdown/Makefile
 create mode 100644 security/fw_lockdown/fw_lockdown.c
security/Kconfig +1 -0
index a4fa8b826039..6e7e5888f823 100644
@@ -243,6 +243,7 @@ source security/tomoyo/Kconfig
 source security/apparmor/Kconfig
 source security/loadpin/Kconfig
 source security/yama/Kconfig
+source security/fw_lockdown/Kconfig
 
 source security/integrity/Kconfig
 
security/Makefile +2 -0
index 8c4a43e3d4e0..58852dee5e22 100644
@@ -9,6 +9,7 @@ subdir-$(CONFIG_SECURITY_TOMOYO)        += tomoyo
 subdir-$(CONFIG_SECURITY_APPARMOR)	+= apparmor
 subdir-$(CONFIG_SECURITY_YAMA)		+= yama
 subdir-$(CONFIG_SECURITY_LOADPIN)	+= loadpin
+subdir-$(CONFIG_SECURITY_FW_LOCKDOWN)	+= fw_lockdown
 
 # always enable default capabilities
 obj-y					+= commoncap.o
@@ -24,6 +25,7 @@ obj-$(CONFIG_SECURITY_TOMOYO)		+= tomoyo/
 obj-$(CONFIG_SECURITY_APPARMOR)		+= apparmor/
 obj-$(CONFIG_SECURITY_YAMA)		+= yama/
 obj-$(CONFIG_SECURITY_LOADPIN)		+= loadpin/
+obj-$(CONFIG_SECURITY_FW_LOCKDOWN)	+= fw_lockdown/
 obj-$(CONFIG_CGROUP_DEVICE)		+= device_cgroup.o
 
 # Object integrity file lists
security/fw_lockdown/Kconfig new file +6 -0
new file mode 100644
index 000000000000..cb7780f7c7f5
@@ -0,0 +1,6 @@
+config SECURITY_FW_LOCKDOWN
+	bool "Prevent loading unsigned firmware"
+	depends on SECURITY && CONFIG_LOCK_DOWN_KERNEL
+	default y
+	help
+	  Prevent loading unsigned firmware in lockdown mode,
security/fw_lockdown/Makefile new file +3 -0
new file mode 100644
index 000000000000..9798a396d4ef
@@ -0,0 +1,3 @@
+obj-$(CONFIG_SECURITY_FW_LOCKDOWN) += fw_lockdown.o
+
+fw_lockdown-y := fw_lockdown.o
security/fw_lockdown/fw_lockdown.c new file +52 -0
new file mode 100644
index 000000000000..15dd6b353eea
@@ -0,0 +1,52 @@
+/*
+ * fw_lockdown security module
+ *
+ * Copyright (C) 2017 IBM Corporation
+ *
+ * Authors:
+ * Mimi Zohar <[email protected]>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ */
+
+#define pr_fmt(fmt) "fw_lockdown: " fmt
+
+#include <linux/module.h>
+#include <linux/binfmts.h>
+#include <linux/namei.h>
+#include <linux/lsm_hooks.h>
+
+/**
+ * fw_lockdown_read_file - prevent loading of unsigned firmware
+ * @file: pointer to firmware
+ * @read_id: caller identifier
+ *
+ * Prevent loading of unsigned firmware in lockdown mode.
+ */
+static int fw_lockdown_read_file(struct file *file, enum kernel_read_file_id id)
+{
+	if (read_id == READING_FIRMWARE) {
+		if (!is_ima_appraise_enabled() &&
+		    kernel_is_locked_down("Loading of unsigned firmware"))
+			return -EACCES;
+	}
+	return 0;
+}
+
+static struct security_hook_list fw_lockdown_hooks[] = {
+	LSM_HOOK_INIT(fw_lockdown_file_check, fw_lockdown_bprm_check)
+};
+
+static int __init init_fw_lockdown(void)
+{
+	security_add_hooks(fw_lockdown_hooks, ARRAY_SIZE(fw_lockdown_hooks),
+			   "fw_lockdown");
+	pr_info("initialized\n");
+	return 0;
+}
+
+late_initcall(init_fw_lockdown);
+MODULE_LICENSE("GPL");
Signature · 1 line
2.7.4
Signature · 2 lines
Luis Rodriguez, SUSE LINUX GmbH
Maxfeldstrasse 5; D-90409 Nuernberg
author
#2 lore raw
Quoted 8 lines · Luis R. Rodriguez
Quoted 6 lines · Mimi Zohar

Hi David,

If you are interested in preventing the loading of unsigned firmware, the patch below is straight forward. ?The patch has ONLY been tested with IMA-appraisal enabled, and works as intended - allowing only signed firmware to be loaded.

Quoted 6 lines

Very nice! This is the sort of thing that I mean by LSM'ifying fw access through a system policy.

We currently handle the LSM aspect for firmware through kernel_read_file_from_path() and so the kernel_read_file LSM hook, so why a new hook here?

kernel_read_file(), itself, is not an LSM hook, but calls two LSM hooks named security_kernel_read_file(), prior to reading a file, and security_kernel_post_read_file(), post reading a file.

In this case, we want to reject even reading the file if it isn't signed, so we're using the security_kernel_read_file() LSM hook.

Quoted 2 lines

Where does this plug in?

This is a standalone, micro LSM that can be configured at build. ?For now I left it is an optional Kconfig parameter, but at some point, you might want to consider making it required.

Mimi

--
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

author
#3 lore raw
In reply to Mimi Zohar

security/fw_lockdown/fw_lockdown.c line 40

Quoted 4 lines · Mimi Zohar
security/fw_lockdown/fw_lockdown.c new file +3 -0
+
+static struct security_hook_list fw_lockdown_hooks[] = {
+	LSM_HOOK_INIT(fw_lockdown_file_check, fw_lockdown_bprm_check)

Sigh, that should have be:
LSM_HOOK_INIT(kernel_read_file, fw_lockdown_read_file)

Quoted 1 line

+};

--
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

#4 lore raw
Quoted 8 lines · Mimi Zohar

security/fw_lockdown/fw_lockdown.c line 40

Quoted 4 lines · Mimi Zohar
security/fw_lockdown/fw_lockdown.c new file +3 -0
+
+static struct security_hook_list fw_lockdown_hooks[] = {
+     LSM_HOOK_INIT(fw_lockdown_file_check, fw_lockdown_bprm_check)

Sigh, that should have be:
LSM_HOOK_INIT(kernel_read_file, fw_lockdown_read_file)

Hah, I thought i was going crazy :) That makes much more sense now!

Luis
--
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