bpf: security: New file mode and LSM hooks for eBPF object permission control
Subsystems (10)
v2 cover bpf: security: New file mode and LSM hooks for eBPF object permission control
From: Chenbo Feng <[email protected]>
Much like files and sockets, eBPF objects are accessed, controlled, and shared via a file descriptor (FD). Unlike files and sockets, the existing mechanism for eBPF object access control is very limited. Currently there are two options for granting accessing to eBPF
operations: grant access to all processes, or only CAP_SYS_ADMIN processes. The CAP_SYS_ADMIN-only mode is not ideal because most users do not have this capability and granting a user CAP_SYS_ADMIN grants too many other security-sensitive permissions. It also unnecessarily allows all CAP_SYS_ADMIN processes access to eBPF functionality. Allowing all processes to access to eBPF objects is also undesirable since it has potential to allow unprivileged processes to consume kernel memory, and opens up attack surface to the kernel.
Adding LSM hooks maintains the status quo for systems which do not use an LSM, preserving compatibility with userspace, while allowing security modules to choose how best to handle permissions on eBPF objects. Here is a possible use case for the lsm hooks with selinux module:
The network-control daemon (netd) creates and loads an eBPF object for network packet filtering and analysis. It passes the object FD to an unprivileged network monitor app (netmonitor), which is not allowed to create, modify or load eBPF objects, but is allowed to read the traffic stats from the map.
Selinux could use these hooks to grant the following permissions:
allow netd self:bpf_map { create read write};
allow netmonitor netd:fd use;
allow netmonitor netd:bpf_map read;
In this patch series, A file mode is added to bpf map to store the accessing mode. With this file mode flags, the map can be obtained read only, write only or read and write. With the help of this file mode, several security hooks can be added to the eBPF syscall implementations to do permissions checks. These LSM hooks are mainly focused on checking the process privileges before it obtains the fd for a specific bpf object. No matter from a file location or from a eBPF id. Besides that, a general check hook is also implemented at the start of bpf syscalls so that each security module can have their own implementation on the reset of bpf object related functionalities.
In order to store the ownership and security information about eBPF maps, a security field pointer is added to the struct bpf_map. And the last two patch set are implementation of selinux check on these hooks introduced, plus an additional check when eBPF object is passed between processes using unix socket as well as binder IPC.
Change since V1:
- Whitelist the new bpf flags in the map allocate check.
- Added bpf selftest for the new flags.
- Added two new security hooks for copying the security information from the bpf object security struct to file security struct
- Simplified the checking action when bpf fd is passed between processes.
Chenbo Feng (5):
bpf: Add file mode configuration into bpf maps
bpf: Add tests for eBPF file mode
security: bpf: Add LSM hooks for bpf object related syscall
selinux: bpf: Add selinux check for eBPF syscall operations
selinux: bpf: Add addtional check for bpf object file receive
include/linux/bpf.h | 15 ++- include/linux/lsm_hooks.h | 71 +++++++++++++ include/linux/security.h | 54 ++++++++++ include/uapi/linux/bpf.h | 6 ++ kernel/bpf/arraymap.c | 7 +- kernel/bpf/devmap.c | 5 +- kernel/bpf/hashtab.c | 5 +- kernel/bpf/inode.c | 15 ++- kernel/bpf/lpm_trie.c | 3 +- kernel/bpf/sockmap.c | 5 +- kernel/bpf/stackmap.c | 5 +- kernel/bpf/syscall.c | 112 ++++++++++++++++++--- security/security.c | 40 ++++++++ security/selinux/hooks.c | 172 ++++++++++++++++++++++++++++++++ security/selinux/include/classmap.h | 2 + security/selinux/include/objsec.h | 4 + tools/testing/selftests/bpf/test_maps.c | 48 +++++++++ 17 files changed, 542 insertions(+), 27 deletions(-)
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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
PATCH v2 1/5 bpf: Add file mode configuration into bpf maps
From: Chenbo Feng <[email protected]>
Introduce the map read/write flags to the eBPF syscalls that returns the map fd. The flags is used to set up the file mode when construct a new file descriptor for bpf maps. To not break the backward capability, the f_flags is set to O_RDWR if the flag passed by syscall is 0. Otherwise it should be O_RDONLY or O_WRONLY. When the userspace want to modify or read the map content, it will check the file mode to see if it is allowed to make the change.
--- include/linux/bpf.h | 6 ++-- include/uapi/linux/bpf.h | 6 ++++ kernel/bpf/arraymap.c | 7 +++-- kernel/bpf/devmap.c | 5 ++- kernel/bpf/hashtab.c | 5 +-- kernel/bpf/inode.c | 15 ++++++--- kernel/bpf/lpm_trie.c | 3 +- kernel/bpf/sockmap.c | 5 ++- kernel/bpf/stackmap.c | 5 ++- kernel/bpf/syscall.c | 80 +++++++++++++++++++++++++++++++++++++++++++----- 10 files changed, 114 insertions(+), 23 deletions(-)
include/linux/bpf.h +4 -2
@@ -308,11 +308,11 @@ void bpf_map_area_free(void *base);extern int sysctl_unprivileged_bpf_disabled; -int bpf_map_new_fd (struct bpf_map *map); +int bpf_map_new_fd (struct bpf_map *map,int flags);int bpf_prog_new_fd (struct bpf_prog *prog);int bpf_obj_pin_user (u32 ufd,const char __user *pathname); -int bpf_obj_get_user (const char __user *pathname); +int bpf_obj_get_user (const char __user *pathname,int flags);int bpf_percpu_hash_copy (struct bpf_map *map,void *key,void *value);int bpf_percpu_array_copy (struct bpf_map *map,void *key,void *value);
@@ -331,6 +331,8 @@ int bpf_fd_htab_map_update_elem(struct bpf_map *map, struct file *map_file, void *key, void *value, u64 map_flags);int bpf_fd_htab_map_lookup_elem (struct bpf_map *map,void *key,u32 *value); +int bpf_get_file_flag (int flags); +/* memcpy that is used with 8-byte aligned pointers, power-of-8 size and * forced to use 'long' read/writes to try to atomically copy long counters. * Best-effort only. No barriers here, since it _will_ race with concurrent
include/uapi/linux/bpf.h +6 -0
@@ -217,6 +217,10 @@ enum bpf_attach_type {#define BPF_OBJ_NAME_LEN 16U +/* Flags for accessing BPF object */ +#define BPF_F_RDONLY (1U << 3) +#define BPF_F_WRONLY (1U << 4) +union bpf_attr {struct {/* anonymous struct used by BPF_MAP_CREATE command */ __u32 map_type;/* one of enum bpf_map_type */
@@ -259,6 +263,7 @@ union bpf_attr {struct {/* anonymous struct used by BPF_OBJ_* commands */ __aligned_u64 pathname;__u32 bpf_fd; +__u32 file_flags; };struct {/* anonymous struct used by BPF_PROG_ATTACH/DETACH commands */
@@ -286,6 +291,7 @@ union bpf_attr {__u32 map_id; };__u32 next_id; +__u32 open_flags; };struct {/* anonymous struct used by BPF_OBJ_GET_INFO_BY_FD */
kernel/bpf/arraymap.c +5 -2
@@ -19,6 +19,9 @@#include "map_in_map.h" +#define ARRAY_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +static void bpf_array_free_percpu (struct bpf_array *array) {int i;
@@ -56,8 +59,8 @@ static struct bpf_map *array_map_alloc(union bpf_attr *attr)/* check sanity of attributes */ if (attr->max_entries ==0 || attr->key_size !=4 || - attr->value_size ==0 || attr->map_flags & ~BPF_F_NUMA_NODE || - (percpu && numa_node !=NUMA_NO_NODE )) + attr->value_size ==0 || attr->map_flags & + ~ARRAY_CREATE_FLAG_MASK || (percpu && numa_node !=NUMA_NO_NODE ))return ERR_PTR (-EINVAL );if (attr->value_size >KMALLOC_MAX_SIZE )
kernel/bpf/devmap.c +4 -1
@@ -50,6 +50,9 @@#include <linux/bpf.h> #include <linux/filter.h> +#define DEV_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +struct bpf_dtab_netdev {struct net_device *dev;struct bpf_dtab *dtab;
@@ -80,7 +83,7 @@ static struct bpf_map *dev_map_alloc(union bpf_attr *attr)/* check sanity of attributes */ if (attr->max_entries ==0 || attr->key_size !=4 || - attr->value_size !=4 || attr->map_flags & ~BPF_F_NUMA_NODE ) + attr->value_size !=4 || attr->map_flags & ~DEV_CREATE_FLAG_MASK )return ERR_PTR (-EINVAL ); dtab =kzalloc (sizeof (*dtab),GFP_USER );
kernel/bpf/hashtab.c +3 -2
@@ -18,8 +18,9 @@#include "bpf_lru_list.h" #include "map_in_map.h" -#define HTAB_CREATE_FLAG_MASK \ - (BPF_F_NO_PREALLOC | BPF_F_NO_COMMON_LRU | BPF_F_NUMA_NODE) +#define HTAB_CREATE_FLAG_MASK \ + (BPF_F_NO_PREALLOC | BPF_F_NO_COMMON_LRU | BPF_F_NUMA_NODE | \ + BPF_F_RDONLY | BPF_F_WRONLY)struct bucket {struct hlist_nulls_head head;
kernel/bpf/inode.c +10 -5
@@ -295,7 +295,7 @@ int bpf_obj_pin_user(u32 ufd, const char __user *pathname) }static void *bpf_obj_do_get (const struct filename *pathname, -enum bpf_type *type) +enum bpf_type *type,int flags) {struct inode *inode;struct path path;
@@ -307,7 +307,7 @@ static void *bpf_obj_do_get(const struct filename *pathname,return ERR_PTR (ret); inode =d_backing_inode (path.dentry); - ret =inode_permission (inode,MAY_WRITE ); + ret =inode_permission (inode,ACC_MODE (flags));if (ret) goto out;
@@ -326,18 +326,23 @@ static void *bpf_obj_do_get(const struct filename *pathname,return ERR_PTR (ret); } -int bpf_obj_get_user (const char __user *pathname) +int bpf_obj_get_user (const char __user *pathname,int flags) {enum bpf_type type =BPF_TYPE_UNSPEC ;struct filename *pname;int ret = -ENOENT ; +int f_flags;void *raw; + f_flags =bpf_get_file_flag (flags); +if (f_flags <0 ) +return f_flags; + pname =getname (pathname);if (IS_ERR (pname))return PTR_ERR (pname); - raw =bpf_obj_do_get (pname, &type); + raw =bpf_obj_do_get (pname, &type, f_flags);if (IS_ERR (raw)) { ret =PTR_ERR (raw); goto out;
@@ -346,7 +351,7 @@ int bpf_obj_get_user(const char __user *pathname)if (type ==BPF_TYPE_PROG ) ret =bpf_prog_new_fd (raw);else if (type ==BPF_TYPE_MAP ) - ret =bpf_map_new_fd (raw); + ret =bpf_map_new_fd (raw, f_flags);else goto out;
kernel/bpf/lpm_trie.c +2 -1
@@ -495,7 +495,8 @@ static int trie_delete_elem(struct bpf_map *map, void *_key)#define LPM_KEY_SIZE_MAX LPM_KEY_SIZE(LPM_DATA_SIZE_MAX)#define LPM_KEY_SIZE_MIN LPM_KEY_SIZE(LPM_DATA_SIZE_MIN) -#define LPM_CREATE_FLAG_MASK (BPF_F_NO_PREALLOC | BPF_F_NUMA_NODE) +#define LPM_CREATE_FLAG_MASK (BPF_F_NO_PREALLOC | BPF_F_NUMA_NODE | \ + BPF_F_RDONLY | BPF_F_WRONLY)static struct bpf_map *trie_alloc (union bpf_attr *attr) {
kernel/bpf/sockmap.c +4 -1
@@ -40,6 +40,9 @@#include <linux/list.h> #include <net/strparser.h> +#define SOCK_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +struct bpf_stab {struct bpf_map map;struct sock **sock_map;
@@ -489,7 +492,7 @@ static struct bpf_map *sock_map_alloc(union bpf_attr *attr)/* check sanity of attributes */ if (attr->max_entries ==0 || attr->key_size !=4 || - attr->value_size !=4 || attr->map_flags & ~BPF_F_NUMA_NODE ) + attr->value_size !=4 || attr->map_flags & ~SOCK_CREATE_FLAG_MASK )return ERR_PTR (-EINVAL );if (attr->value_size >KMALLOC_MAX_SIZE )
kernel/bpf/stackmap.c +4 -1
@@ -11,6 +11,9 @@#include <linux/perf_event.h> #include "percpu_freelist.h" +#define STACK_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +struct stack_map_bucket {struct pcpu_freelist_node fnode;u32 hash;
@@ -60,7 +63,7 @@ static struct bpf_map *stack_map_alloc(union bpf_attr *attr)if (!capable (CAP_SYS_ADMIN ))return ERR_PTR (-EPERM ); -if (attr->map_flags & ~BPF_F_NUMA_NODE ) +if (attr->map_flags & ~STACK_CREATE_FLAG_MASK )return ERR_PTR (-EINVAL );/* check sanity of attributes */
kernel/bpf/syscall.c +72 -8
181 lines not on this page · raw message
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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@ http://vger.kernel.org/majordomo-info.html
Re: [PATCH net-next v2 1/5] bpf: Add file mode configuration into bpf maps
Quoted 98 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce the map read/write flags to the eBPF syscalls that returns the map fd. The flags is used to set up the file mode when construct a new file descriptor for bpf maps. To not break the backward capability, the
f_flagsis set toO_RDWRif the flag passed by syscall is 0. Otherwise it should beO_RDONLYorO_WRONLY. When the userspace want to modify or read the map content, it will check the file mode to see if it is allowed to make the change.Signed-off-by Chenbo Feng <[email protected]>--- include/linux/bpf.h | 6 ++-- include/uapi/linux/bpf.h | 6 ++++ kernel/bpf/arraymap.c | 7 +++-- kernel/bpf/devmap.c | 5 ++- kernel/bpf/hashtab.c | 5 +-- kernel/bpf/inode.c | 15 ++++++--- kernel/bpf/lpm_trie.c | 3 +- kernel/bpf/sockmap.c | 5 ++- kernel/bpf/stackmap.c | 5 ++- kernel/bpf/syscall.c | 80 +++++++++++++++++++++++++++++++++++++++++++----- 10 files changed, 114 insertions(+), 23 deletions(-)include/linux/bpf.h +4
-2@@ -308,11 +308,11 @@ void bpf_map_area_free(void *base);extern int sysctl_unprivileged_bpf_disabled; -int bpf_map_new_fd (struct bpf_map *map); +int bpf_map_new_fd (struct bpf_map *map,int flags);int bpf_prog_new_fd (struct bpf_prog *prog);int bpf_obj_pin_user (u32 ufd,const char __user *pathname); -int bpf_obj_get_user (const char __user *pathname); +int bpf_obj_get_user (const char __user *pathname,int flags);int bpf_percpu_hash_copy (struct bpf_map *map,void *key,void *value);int bpf_percpu_array_copy (struct bpf_map *map,void *key,void *value);@@ -331,6 +331,8 @@ int bpf_fd_htab_map_update_elem(struct bpf_map *map, struct file *map_file, void *key, void *value, u64 map_flags);int bpf_fd_htab_map_lookup_elem (struct bpf_map *map,void *key,u32 *value); +int bpf_get_file_flag (int flags); +/* memcpy that is used with 8-byte aligned pointers, power-of-8 size and * forced to use 'long' read/writes to try to atomically copy long counters. * Best-effort only. No barriers here, since it _will_ race with concurrent include/uapi/linux/bpf.h +6
-0@@ -217,6 +217,10 @@ enum bpf_attach_type {#define BPF_OBJ_NAME_LEN 16U +/* Flags for accessing BPF object */ +#define BPF_F_RDONLY (1U << 3) +#define BPF_F_WRONLY (1U << 4) +union bpf_attr {struct {/* anonymous struct used by BPF_MAP_CREATE command */ __u32 map_type;/* one of enum bpf_map_type */ @@ -259,6 +263,7 @@ union bpf_attr {struct {/* anonymous struct used by BPF_OBJ_* commands */ __aligned_u64 pathname;__u32 bpf_fd; +__u32 file_flags; };struct {/* anonymous struct used by BPF_PROG_ATTACH/DETACH commands */ @@ -286,6 +291,7 @@ union bpf_attr {__u32 map_id; };__u32 next_id; +__u32 open_flags; };struct {/* anonymous struct used by BPF_OBJ_GET_INFO_BY_FD */ kernel/bpf/arraymap.c +3
-0@@ -19,6 +19,9 @@#include "map_in_map.h" +#define ARRAY_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +static void bpf_array_free_percpu (struct bpf_array *array) {int i;
kernel/bpf/arraymap.c static struct bpf_map *array_map_alloc(union bpf_attr *attr) · line 63
Quoted 7 lines
kernel/bpf/arraymap.c +2
-2@@ -56,8 +59,8 @@ static struct bpf_map *array_map_alloc(union bpf_attr *attr)/* check sanity of attributes */ if (attr->max_entries ==0 || attr->key_size !=4 || - attr->value_size ==0 || attr->map_flags & ~BPF_F_NUMA_NODE || - (percpu && numa_node !=NUMA_NO_NODE )) + attr->value_size ==0 || attr->map_flags & + ~ARRAY_CREATE_FLAG_MASK || (percpu && numa_node !=NUMA_NO_NODE ))
that's very non-standard way of breaking lines.
Did you run checkpatch ? did it complain?
--
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
Re: [PATCH net-next v2 1/5] bpf: Add file mode configuration into bpf maps
Quoted 100 lines · Alexei Starovoitov
Quoted 99 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce the map read/write flags to the eBPF syscalls that returns the map fd. The flags is used to set up the file mode when construct a new file descriptor for bpf maps. To not break the backward capability, the
f_flagsis set toO_RDWRif the flag passed by syscall is 0. Otherwise it should beO_RDONLYorO_WRONLY. When the userspace want to modify or read the map content, it will check the file mode to see if it is allowed to make the change.Signed-off-by Chenbo Feng <[email protected]>--- include/linux/bpf.h | 6 ++-- include/uapi/linux/bpf.h | 6 ++++ kernel/bpf/arraymap.c | 7 +++-- kernel/bpf/devmap.c | 5 ++- kernel/bpf/hashtab.c | 5 +-- kernel/bpf/inode.c | 15 ++++++--- kernel/bpf/lpm_trie.c | 3 +- kernel/bpf/sockmap.c | 5 ++- kernel/bpf/stackmap.c | 5 ++- kernel/bpf/syscall.c | 80 +++++++++++++++++++++++++++++++++++++++++++----- 10 files changed, 114 insertions(+), 23 deletions(-)include/linux/bpf.h +4
-2@@ -308,11 +308,11 @@ void bpf_map_area_free(void *base);extern int sysctl_unprivileged_bpf_disabled; -int bpf_map_new_fd (struct bpf_map *map); +int bpf_map_new_fd (struct bpf_map *map,int flags);int bpf_prog_new_fd (struct bpf_prog *prog);int bpf_obj_pin_user (u32 ufd,const char __user *pathname); -int bpf_obj_get_user (const char __user *pathname); +int bpf_obj_get_user (const char __user *pathname,int flags);int bpf_percpu_hash_copy (struct bpf_map *map,void *key,void *value);int bpf_percpu_array_copy (struct bpf_map *map,void *key,void *value);@@ -331,6 +331,8 @@ int bpf_fd_htab_map_update_elem(struct bpf_map *map, struct file *map_file, void *key, void *value, u64 map_flags);int bpf_fd_htab_map_lookup_elem (struct bpf_map *map,void *key,u32 *value); +int bpf_get_file_flag (int flags); +/* memcpy that is used with 8-byte aligned pointers, power-of-8 size and * forced to use 'long' read/writes to try to atomically copy long counters. * Best-effort only. No barriers here, since it _will_ race with concurrent include/uapi/linux/bpf.h +6
-0@@ -217,6 +217,10 @@ enum bpf_attach_type {#define BPF_OBJ_NAME_LEN 16U +/* Flags for accessing BPF object */ +#define BPF_F_RDONLY (1U << 3) +#define BPF_F_WRONLY (1U << 4) +union bpf_attr {struct {/* anonymous struct used by BPF_MAP_CREATE command */ __u32 map_type;/* one of enum bpf_map_type */ @@ -259,6 +263,7 @@ union bpf_attr {struct {/* anonymous struct used by BPF_OBJ_* commands */ __aligned_u64 pathname;__u32 bpf_fd; +__u32 file_flags; };struct {/* anonymous struct used by BPF_PROG_ATTACH/DETACH commands */ @@ -286,6 +291,7 @@ union bpf_attr {__u32 map_id; };__u32 next_id; +__u32 open_flags; };struct {/* anonymous struct used by BPF_OBJ_GET_INFO_BY_FD */ kernel/bpf/arraymap.c +3
-0@@ -19,6 +19,9 @@#include "map_in_map.h" +#define ARRAY_CREATE_FLAG_MASK \ + (BPF_F_NUMA_NODE | BPF_F_RDONLY | BPF_F_WRONLY) +static void bpf_array_free_percpu (struct bpf_array *array) {int i;@@ -56,8 +59,8 @@ static struct bpf_map *array_map_alloc(union bpf_attr *attr)
Quoted 10 lines
kernel/bpf/arraymap.c static struct bpf_map *array_map_alloc(union bpf_attr *attr) · line 63
Quoted 6 lines
kernel/bpf/arraymap.c +2
-2/* check sanity of attributes */ if (attr->max_entries ==0 || attr->key_size !=4 || - attr->value_size ==0 || attr->map_flags & ~BPF_F_NUMA_NODE || - (percpu && numa_node !=NUMA_NO_NODE )) + attr->value_size ==0 || attr->map_flags & + ~ARRAY_CREATE_FLAG_MASK || (percpu && numa_node !=NUMA_NO_NODE ))that's very non-standard way of breaking lines.
Did you run checkpatch ? did it complain?
Will fix in next revision, checkpatch didn't say anything about this....0 error and 0 warning for this patch series.
--
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
PATCH v2 2/5 bpf: Add tests for eBPF file mode
In reply to Chenbo FengFrom: Chenbo Feng <[email protected]>
Two related tests are added into bpf selftest to test read only map and write only map. The tests verified the read only and write only flags are working on hash maps.
--- tools/testing/selftests/bpf/test_maps.c | 48 +++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+)
tools/testing/selftests/bpf/test_maps.c +48 -0
@@ -1033,6 +1033,51 @@ static void test_map_parallel(void)assert (bpf_map_get_next_key (fd, &key, &key) ==-1 && errno ==ENOENT ); } +static void test_map_rdonly (void ) +{ +int i, fd, key =0 , value =0 ; + + fd =bpf_create_map (BPF_MAP_TYPE_HASH ,sizeof (key),sizeof (value), +MAP_SIZE , map_flags |BPF_F_RDONLY ); +if (fd <0 ) { +printf ("Failed to create map for read only test '%s'!\n" , +strerror (errno)); +exit (1 ); + } + + key =1 ; + value =1234 ; +/* Insert key=1 element. */ +assert (bpf_map_update_elem (fd, &key, &value,BPF_ANY ) ==-1 && + errno ==EPERM ); + +/* Check that key=2 is not found. */ +assert (bpf_map_lookup_elem (fd, &key, &value) ==-1 && errno ==ENOENT ); +assert (bpf_map_get_next_key (fd, &key, &value) ==-1 && errno ==ENOENT ); +} + +static void test_map_wronly (void ) +{ +int i, fd, key =0 , value =0 ; + + fd =bpf_create_map (BPF_MAP_TYPE_HASH ,sizeof (key),sizeof (value), +MAP_SIZE , map_flags |BPF_F_WRONLY ); +if (fd <0 ) { +printf ("Failed to create map for read only test '%s'!\n" , +strerror (errno)); +exit (1 ); + } + + key =1 ; + value =1234 ; +/* Insert key=1 element. */ +assert (bpf_map_update_elem (fd, &key, &value,BPF_ANY ) ==0 ) + + /* Check that key=2 is not found. */ +assert (bpf_map_lookup_elem (fd, &key, &value) ==-1 && errno ==EPERM ); +assert (bpf_map_get_next_key (fd, &key, &value) ==-1 && errno ==EPERM ); +} +static void run_all_tests (void ) {test_hashmap (0 ,NULL );
@@ -1050,6 +1095,9 @@ static void run_all_tests(void)test_map_large ();test_map_parallel ();test_map_stress (); + +test_map_rdonly (); +test_map_wronly (); }int main (void )
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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@ http://vger.kernel.org/majordomo-info.html
PATCH v2 3/5 security: bpf: Add LSM hooks for bpf object related syscall
In reply to Chenbo FengFrom: Chenbo Feng <[email protected]>
Introduce several LSM hooks for the syscalls that will allow the userspace to access to eBPF object such as eBPF programs and eBPF maps. The security check is aimed to enforce a per object security protection for eBPF object so only processes with the right priviliges can read/write to a specific map or use a specific eBPF program. Besides that, a general security hook is added before the multiplexer of bpf syscall to check the cmd and the attribute used for the command. The actual security module can decide which command need to be checked and how the cmd should be checked.
--- include/linux/bpf.h | 6 ++++++ include/linux/lsm_hooks.h | 54 +++++++++++++++++++++++++++++++++++++++++++++++ include/linux/security.h | 45 +++++++++++++++++++++++++++++++++++++++ kernel/bpf/syscall.c | 28 ++++++++++++++++++++++-- security/security.c | 32 ++++++++++++++++++++++++++++ 5 files changed, 163 insertions(+), 2 deletions(-)
include/linux/bpf.h +6 -0
@@ -57,6 +57,9 @@ struct bpf_map {atomic_t usercnt;struct bpf_map *inner_map_meta;char name[BPF_OBJ_NAME_LEN ]; +#ifdef CONFIG_SECURITY +void *security; +#endif };/* function argument constraints */
@@ -190,6 +193,9 @@ struct bpf_prog_aux {struct user_struct *user;u64 load_time;/* ns since boottime */ char name[BPF_OBJ_NAME_LEN ]; +#ifdef CONFIG_SECURITY +void *security; +#endif union {struct work_struct work;struct rcu_head rcu;
include/linux/lsm_hooks.h +54 -0
72 lines not on this page · raw message
include/linux/security.h +45 -0
57 lines not on this page · raw message
kernel/bpf/syscall.c +26 -2
@@ -210,6 +210,7 @@ static void bpf_map_free_deferred(struct work_struct *work) struct bpf_map *map = container_of(work, struct bpf_map, work);bpf_map_uncharge_memlock (map); +security_bpf_map_free (map);/* implementation dependent freeing */ map->ops->map_free (map); }
@@ -323,6 +324,9 @@ static const struct file_operations bpf_map_fops = {int bpf_map_new_fd (struct bpf_map *map,int flags) { +if (security_bpf_map (map,OPEN_FMODE (flags))) +return -EPERM ; +return anon_inode_getfd ("bpf-map" , &bpf_map_fops, map, flags |O_CLOEXEC ); }
@@ -403,10 +407,14 @@ static int map_create(union bpf_attr *attr)atomic_set (&map->refcnt,1 );atomic_set (&map->usercnt,1 ); - err =bpf_map_charge_memlock (map); + err =security_bpf_map_alloc (map);if (err) goto free_map_nouncharge; + err =bpf_map_charge_memlock (map); +if (err) + goto free_map_sec; + err =bpf_map_alloc_id (map);if (err) goto free_map;
@@ -428,6 +436,8 @@ static int map_create(union bpf_attr *attr) free_map:bpf_map_uncharge_memlock (map); +free_map_sec: +security_bpf_map_free (map); free_map_nouncharge: map->ops->map_free (map);return err;
@@ -906,6 +916,7 @@ static void __bpf_prog_put_rcu(struct rcu_head *rcu)free_used_maps (aux);bpf_prog_uncharge_memlock (aux->prog); +security_bpf_prog_free (aux);bpf_prog_free (aux->prog); }
@@ -964,6 +975,9 @@ static const struct file_operations bpf_prog_fops = {int bpf_prog_new_fd (struct bpf_prog *prog) { +if (security_bpf_prog (prog)) +return -EPERM ; +return anon_inode_getfd ("bpf-prog" , &bpf_prog_fops, prog,O_RDWR |O_CLOEXEC ); }
@@ -1103,10 +1117,14 @@ static int bpf_prog_load(union bpf_attr *attr)if (!prog)return -ENOMEM ; - err =bpf_prog_charge_memlock (prog); + err =security_bpf_prog_alloc (prog->aux);if (err) goto free_prog_nouncharge; + err =bpf_prog_charge_memlock (prog); +if (err) + goto free_prog_sec; + prog->len = attr->insn_cnt; err = -EFAULT ;
@@ -1164,6 +1182,8 @@ static int bpf_prog_load(union bpf_attr *attr)free_used_maps (prog->aux); free_prog:bpf_prog_uncharge_memlock (prog); +free_prog_sec: +security_bpf_prog_free (prog->aux); free_prog_nouncharge:bpf_prog_free (prog);return err;
@@ -1630,6 +1650,10 @@ SYSCALL_DEFINE3(bpf, int, cmd, union bpf_attr __user *, uattr, unsigned int, sizif (copy_from_user (&attr, uattr, size) !=0 )return -EFAULT ; + err =security_bpf (cmd, &attr, size); +if (err) +return -EPERM ; +switch (cmd) {case BPF_MAP_CREATE : err =map_create (&attr);
security/security.c +32 -0
@@ -12,6 +12,7 @@* (at your option) any later version. */ +#include <linux/bpf.h> #include <linux/capability.h> #include <linux/dcache.h> #include <linux/module.h>
@@ -1703,3 +1704,34 @@ int security_audit_rule_match(u32 secid, u32 field, u32 op, void *lsmrule, actx); }#endif /* CONFIG_AUDIT */ + +#ifdef CONFIG_BPF_SYSCALL +int security_bpf (int cmd,union bpf_attr *attr,unsigned int size) +{ +return call_int_hook (bpf,0 , cmd, attr, size); +} +int security_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +return call_int_hook (bpf_map,0 , map, fmode); +} +int security_bpf_prog (struct bpf_prog *prog) +{ +return call_int_hook (bpf_prog,0 , prog); +} +int security_bpf_map_alloc (struct bpf_map *map) +{ +return call_int_hook (bpf_map_alloc_security,0 , map); +} +int security_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +return call_int_hook (bpf_prog_alloc_security,0 , aux); +} +void security_bpf_map_free (struct bpf_map *map) +{ +call_void_hook (bpf_map_free_security, map); +} +void security_bpf_prog_free (struct bpf_prog_aux *aux) +{ +call_void_hook (bpf_prog_free_security, aux); +} +#endif /* CONFIG_BPF_SYSCALL */
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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
PATCH v2 4/5 selinux: bpf: Add selinux check for eBPF syscall operations
In reply to Chenbo FengFrom: Chenbo Feng <[email protected]>
Implement the actual checks introduced to eBPF related syscalls. This implementation use the security field inside bpf object to store a sid that identify the bpf object. And when processes try to access the object, selinux will check if processes have the right privileges. The creation of eBPF object are also checked at the general bpf check hook and new cmd introduced to eBPF domain can also be checked there.
--- security/selinux/hooks.c | 111 ++++++++++++++++++++++++++++++++++++ security/selinux/include/classmap.h | 2 + security/selinux/include/objsec.h | 4 ++ 3 files changed, 117 insertions(+)
security/selinux/hooks.c +111 -0
@@ -85,6 +85,7 @@#include <linux/export.h> #include <linux/msg.h> #include <linux/shm.h> +#include <linux/bpf.h> #include "avc.h" #include "objsec.h"
@@ -6252,6 +6253,106 @@ static void selinux_ib_free_security(void *ib_sec) }#endif +#ifdef CONFIG_BPF_SYSCALL +static int selinux_bpf (int cmd,union bpf_attr *attr, +unsigned int size) +{ +u32 sid =current_sid (); +int ret; + +switch (cmd) { +case BPF_MAP_CREATE : + ret =avc_has_perm (sid, sid,SECCLASS_BPF_MAP ,BPF_MAP__CREATE , +NULL ); +break ; +case BPF_PROG_LOAD : + ret =avc_has_perm (sid, sid,SECCLASS_BPF_PROG ,BPF_PROG__LOAD , +NULL ); +break ; +default : + ret =0 ; +break ; + } + +return ret; +} + +static u32 bpf_map_fmode_to_av (fmode_t fmode) +{ +u32 av =0 ; + +if (f_mode &FMODE_READ ) + av |=BPF_MAP__READ ; +if (f_mode &FMODE_WRITE ) + av |=BPF_MAP__WRITE ; +return av; +} + +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = map->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_MAP , +bpf_map_fmode_to_av (fmode),NULL ); +} + +static int selinux_bpf_prog (struct bpf_prog *prog) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = prog->aux->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_PROG , +BPF_PROG__USE ,NULL ); +} + +static int selinux_bpf_map_alloc (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + map->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_map_free (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec = map->security; + + map->security =NULL ; +kfree (bpfsec); +} + +static int selinux_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + aux->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_prog_free (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec = aux->security; + + aux->security =NULL ; +kfree (bpfsec); +} +#endif + static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = {LSM_HOOK_INIT (binder_set_context_mgr, selinux_binder_set_context_mgr),LSM_HOOK_INIT (binder_transaction, selinux_binder_transaction),
@@ -6471,6 +6572,16 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { LSM_HOOK_INIT(audit_rule_match, selinux_audit_rule_match), LSM_HOOK_INIT(audit_rule_free, selinux_audit_rule_free),#endif + +#ifdef CONFIG_BPF_SYSCALL +LSM_HOOK_INIT (bpf, selinux_bpf), +LSM_HOOK_INIT (bpf_map, selinux_bpf_map), +LSM_HOOK_INIT (bpf_prog, selinux_bpf_prog), +LSM_HOOK_INIT (bpf_map_alloc_security, selinux_bpf_map_alloc), +LSM_HOOK_INIT (bpf_prog_alloc_security, selinux_bpf_prog_alloc), +LSM_HOOK_INIT (bpf_map_free_security, selinux_bpf_map_free), + LSM_HOOK_INIT(bpf_prog_free_security, selinux_bpf_prog_free), +#endif };static __init int selinux_init (void )
security/selinux/include/classmap.h +2 -0
@@ -237,6 +237,8 @@ struct security_class_mapping secclass_map[] = { { "access", NULL } }, {"infiniband_endport" , { "manage_subnet", NULL } }, + { "bpf_map", {"create", "read", "write"} }, + { "bpf_prog", {"load", "use"} }, { NULL } };
security/selinux/include/objsec.h +4 -0
@@ -150,6 +150,10 @@ struct pkey_security_struct { u32 sid; /* SID of pkey */ }; +struct bpf_security_struct { +u32 sid;/*SID of bpf obj creater*/ +}; +extern unsigned int selinux_checkreqprot;#endif /* _SELINUX_OBJSEC_H_ */
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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
Re: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
Quoted 172 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Implement the actual checks introduced to eBPF related syscalls. This implementation use the security field inside bpf object to store a sid that
identify the bpf object. And when processes try to access the object, selinux will check if processes have the right privileges. The creation
of eBPF object are also checked at the general bpf check hook and new cmd introduced to eBPF domain can also be checked there.Signed-off-by Chenbo Feng <[email protected]>---
?security/selinux/hooks.c????????????| 111
++++++++++++++++++++++++++++++++++++
?security/selinux/include/classmap.h |???2 +
?security/selinux/include/objsec.h???|???4 ++
?3 files changed, 117 insertions(+)security/selinux/hooks.c +0
-0@@ -85,6 +85,7 @@?#include <
linux/export.h>
?#include <linux/msg.h>
?#include <linux/shm.h>
+#include <linux/bpf.h>
?
?#include "avc.h"
?#include "objsec.h"security/selinux/hooks.c +0
-0@@ -6252,6 +6253,106 @@ static void selinux_ib_free_security(void *ib_sec) ?}?#endif
?security/selinux/hooks.c +10
-0+#ifdef CONFIG_BPF_SYSCALL +static int selinux_bpf (int cmd,union bpf_attr *attr, + ?????unsigned int size) +{ +u32 sid =current_sid (); +int ret; + +switch (cmd) { +case BPF_MAP_CREATE : + ret = avc_has_perm(sid, sid, SECCLASS_BPF_MAP,
BPF_MAP__CREATE,security/selinux/hooks.c +4
-0+ ???NULL); +break ; +case BPF_PROG_LOAD : + ret = avc_has_perm(sid, sid, SECCLASS_BPF_PROG,
BPF_PROG__LOAD,security/selinux/hooks.c +86
-0+ ???NULL); +break ; +default : + ret =0 ; + break; + } + +return ret; +} + +static u32 bpf_map_fmode_to_av (fmode_t fmode) +{ +u32 av =0 ; + +if (f_mode &FMODE_READ ) + av |=BPF_MAP__READ ; +if (f_mode &FMODE_WRITE ) + av |=BPF_MAP__WRITE ; +return av; +} + +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = map->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_MAP , + ????bpf_map_fmode_to_av(fmode), NULL); +} + +static int selinux_bpf_prog (struct bpf_prog *prog) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = prog->aux->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_PROG , + ????BPF_PROG__USE, NULL); +} + +static int selinux_bpf_map_alloc (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + map->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_map_free (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec = map->security; + + map->security =NULL ; +kfree (bpfsec); +} + +static int selinux_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + aux->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_prog_free (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec = aux->security; + + aux->security =NULL ; +kfree (bpfsec); +} +#endif +?static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init= {
? LSM_HOOK_INIT(binder_set_context_mgr,selinux_binder_set_context_mgr),
? LSM_HOOK_INIT(binder_transaction,selinux_binder_transaction),security/selinux/hooks.c +0
-0@@ -6471,6 +6572,16 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { ? LSM_HOOK_INIT(audit_rule_match, selinux_audit_rule_match), ? LSM_HOOK_INIT(audit_rule_free, selinux_audit_rule_free),?#endif
security/selinux/hooks.c +6
-0+ +#ifdef CONFIG_BPF_SYSCALL +LSM_HOOK_INIT (bpf, selinux_bpf), +LSM_HOOK_INIT (bpf_map, selinux_bpf_map), +LSM_HOOK_INIT (bpf_prog, selinux_bpf_prog), + LSM_HOOK_INIT(bpf_map_alloc_security,
selinux_bpf_map_alloc),security/selinux/hooks.c +1
-0+ LSM_HOOK_INIT(bpf_prog_alloc_security,
selinux_bpf_prog_alloc),security/selinux/hooks.c +2
-0+LSM_HOOK_INIT (bpf_map_free_security, selinux_bpf_map_free), + LSM_HOOK_INIT(bpf_prog_free_security,
selinux_bpf_prog_free),
+#endif
?};
?
?static__initintselinux_init(void)security/selinux/include/classmap.h +0
-0
security/selinux/include/classmap.h struct security_class_mapping secclass_map[] = { · line 241
Quoted 5 lines
security/selinux/include/classmap.h +2
-0@@ -237,6 +237,8 @@ struct security_class_mapping secclass_map[] = { ? ??{ "access", NULL } }, ? { "infiniband_endport", ? ??{ "manage_subnet", NULL } }, + { "bpf_map", {"create", "read", "write"} }, + { "bpf_prog", {"load", "use"} },
Again I have to ask: do you truly need/want two separate classes, or would a single class with distinct permissions suffice, ala:
????????{ "bpf", { "create_map", "read_map", "write_map", "prog_load", "prog_use" } },
and then allow A self:bpf { create_map read_map write_map prog_load prog_use }; would be stored in a single policy avtab rule, and be cached in a single AVC entry.
Quoted 16 lines
security/selinux/include/classmap.h +0
-0? { NULL } ???};?
security/selinux/include/objsec.h +0
-0@@ -150,6 +150,10 @@ struct pkey_security_struct {? u32 sid; /* SID of pkey */
?};
?security/selinux/include/objsec.h +4
-0+struct bpf_security_struct { + u32 sid;??/*SID of bpf obj creater*/ +}; +
Quoted 3 lines
?extern unsigned int
selinux_checkreqprot;
?
?#endif /* _SELINUX_OBJSEC_H_ */
--
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
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
Quoted 191 lines · Stephen Smalley
Quoted 177 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Implement the actual checks introduced to eBPF related syscalls. This
implementation use the security field inside bpf object to store a sid that
identify the bpf object. And when processes try to access the object,
selinux will check if processes have the right privileges. The creation
of eBPF object are also checked at the general bpf check hook and new
cmd introduced to eBPF domain can also be checked there.Signed-off-by Chenbo Feng <[email protected]>---
?security/selinux/hooks.c????????????| 111
++++++++++++++++++++++++++++++++++++
?security/selinux/include/classmap.h |???2 +
?security/selinux/include/objsec.h???|???4 ++
?3 files changed, 117 insertions(+)security/selinux/hooks.c +0
-0@@ -85,6 +85,7 @@?#include <
linux/export.h>
?#include <linux/msg.h>
?#include <linux/shm.h>
+#include <linux/bpf.h>
?
?#include "avc.h"
?#include "objsec.h"security/selinux/hooks.c +0
-0@@ -6252,6 +6253,106 @@ static void selinux_ib_free_security(void *ib_sec) ?}?#endif
?security/selinux/hooks.c +10
-0+#ifdef CONFIG_BPF_SYSCALL +static int selinux_bpf (int cmd,union bpf_attr *attr, + ?????unsigned int size) +{ +u32 sid =current_sid (); +int ret; + +switch (cmd) { +case BPF_MAP_CREATE : + ret = avc_has_perm(sid, sid, SECCLASS_BPF_MAP,
BPF_MAP__CREATE,security/selinux/hooks.c +4
-0+ ???NULL); +break ; +case BPF_PROG_LOAD : + ret = avc_has_perm(sid, sid, SECCLASS_BPF_PROG,
BPF_PROG__LOAD,security/selinux/hooks.c +86
-0+ ???NULL); +break ; +default : + ret =0 ; + break; + } + +return ret; +} + +static u32 bpf_map_fmode_to_av (fmode_t fmode) +{ +u32 av =0 ; + +if (f_mode &FMODE_READ ) + av |=BPF_MAP__READ ; +if (f_mode &FMODE_WRITE ) + av |=BPF_MAP__WRITE ; +return av; +} + +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = map->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_MAP , + ????bpf_map_fmode_to_av(fmode), NULL); +} + +static int selinux_bpf_prog (struct bpf_prog *prog) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = prog->aux->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_PROG , + ????BPF_PROG__USE, NULL); +} + +static int selinux_bpf_map_alloc (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + map->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_map_free (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec = map->security; + + map->security =NULL ; +kfree (bpfsec); +} + +static int selinux_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + aux->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_prog_free (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec = aux->security; + + aux->security =NULL ; +kfree (bpfsec); +} +#endif +?static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {
? LSM_HOOK_INIT(binder_set_context_mgr,selinux_binder_set_context_mgr),
? LSM_HOOK_INIT(binder_transaction,selinux_binder_transaction),security/selinux/hooks.c +0
-0@@ -6471,6 +6572,16 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { ? LSM_HOOK_INIT(audit_rule_match, selinux_audit_rule_match), ? LSM_HOOK_INIT(audit_rule_free, selinux_audit_rule_free),?#endif
security/selinux/hooks.c +6
-0+ +#ifdef CONFIG_BPF_SYSCALL +LSM_HOOK_INIT (bpf, selinux_bpf), +LSM_HOOK_INIT (bpf_map, selinux_bpf_map), +LSM_HOOK_INIT (bpf_prog, selinux_bpf_prog), + LSM_HOOK_INIT(bpf_map_alloc_security,
selinux_bpf_map_alloc),security/selinux/hooks.c +1
-0+ LSM_HOOK_INIT(bpf_prog_alloc_security,
selinux_bpf_prog_alloc),security/selinux/hooks.c +1
-0+ LSM_HOOK_INIT(bpf_map_free_security,
selinux_bpf_map_free),security/selinux/hooks.c +1
-0+ LSM_HOOK_INIT(bpf_prog_free_security,
selinux_bpf_prog_free),
+#endif
?};
?
?static__initintselinux_init(void)security/selinux/include/classmap.h +0
-0security/selinux/include/classmap.h struct security_class_mapping secclass_map[] = · line 242
Quoted 6 lines
security/selinux/include/classmap.h +2
-0@@ -237,6 +237,8 @@ struct security_class_mapping secclass_map[] = { ? ??{ "access", NULL } }, ? { "infiniband_endport", ? ??{ "manage_subnet", NULL } }, + { "bpf_map", {"create", "read", "write"} }, + { "bpf_prog", {"load", "use"} },Again I have to ask: do you truly need/want two separate classes, or would a single class with distinct permissions suffice, ala:
????????{ "bpf", { "create_map", "read_map", "write_map", "prog_load",
"prog_use" } },
Quoted 3 lines
and then allow A self:bpf {
create_mapread_mapwrite_mapprog_loadprog_use}; would be stored in a single policy avtab rule, and be cached in a single AVC entry.
I guess for consistency in naming it should be either:
????????{ "bpf", { "map_create", "map_read", "map_write", "prog_load", "prog_use" } },
?
or:
????????{ "bpf", { "create_map", "read_map", "write_map", "load_prog", "use_prog" } },
?
Quoted 11 lines
Quoted 11 lines
security/selinux/include/classmap.h +0
-0? { NULL } ???};?
security/selinux/include/objsec.h +0
-0@@ -150,6 +150,10 @@ struct pkey_security_struct {? u32 sid; /* SID of pkey */
?};
Quoted 8 lines
Quoted 8 lines
?
security/selinux/include/objsec.h +4
-0+struct bpf_security_struct { + u32 sid;??/*SID of bpf obj creater*/ +}; +?extern unsigned int
selinux_checkreqprot;
?
?#endif /* _SELINUX_OBJSEC_H_ */
--
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
Re: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
Quoted 192 lines · Stephen Smalley
Quoted 191 lines · Stephen Smalley
Quoted 177 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Implement the actual checks introduced to eBPF related syscalls. This
implementation use the security field inside bpf object to store a sid that
identify the bpf object. And when processes try to access the object,
selinux will check if processes have the right privileges. The creation
of eBPF object are also checked at the general bpf check hook and new
cmd introduced to eBPF domain can also be checked there.Signed-off-by Chenbo Feng <[email protected]>--- security/selinux/hooks.c | 111 ++++++++++++++++++++++++++++++++++++ security/selinux/include/classmap.h | 2 + security/selinux/include/objsec.h | 4 ++ 3 files changed, 117 insertions(+)security/selinux/hooks.c +101
-0@@ -85,6 +85,7 @@#include <linux/export.h> #include <linux/msg.h> #include <linux/shm.h> +#include <linux/bpf.h> #include "avc.h" #include "objsec.h" @@ -6252,6 +6253,106 @@ static void selinux_ib_free_security(void *ib_sec) }#endif +#ifdef CONFIG_BPF_SYSCALL +static int selinux_bpf (int cmd,union bpf_attr *attr, +unsigned int size) +{ +u32 sid =current_sid (); +int ret; + +switch (cmd) { +case BPF_MAP_CREATE : + ret =avc_has_perm (sid, sid,SECCLASS_BPF_MAP ,BPF_MAP__CREATE , +NULL ); +break ; +case BPF_PROG_LOAD : + ret =avc_has_perm (sid, sid,SECCLASS_BPF_PROG ,BPF_PROG__LOAD , +NULL ); +break ; +default : + ret =0 ; +break ; + } + +return ret; +} + +static u32 bpf_map_fmode_to_av (fmode_t fmode) +{ +u32 av =0 ; + +if (f_mode &FMODE_READ ) + av |=BPF_MAP__READ ; +if (f_mode &FMODE_WRITE ) + av |=BPF_MAP__WRITE ; +return av; +} + +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = map->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_MAP , +bpf_map_fmode_to_av (fmode),NULL ); +} + +static int selinux_bpf_prog (struct bpf_prog *prog) +{ +u32 sid =current_sid (); +struct bpf_security_struct *bpfsec; + + bpfsec = prog->aux->security; +return avc_has_perm (sid, bpfsec->sid,SECCLASS_BPF_PROG , +BPF_PROG__USE ,NULL ); +} + +static int selinux_bpf_map_alloc (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + map->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_map_free (struct bpf_map *map) +{ +struct bpf_security_struct *bpfsec = map->security; + + map->security =NULL ; +kfree (bpfsec); +} + +static int selinux_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec; + + bpfsec =kzalloc (sizeof (*bpfsec),GFP_KERNEL ); +if (!bpfsec) +return -ENOMEM ; + + bpfsec->sid =current_sid (); + aux->security = bpfsec; + +return 0 ; +} + +static void selinux_bpf_prog_free (struct bpf_prog_aux *aux) +{ +struct bpf_security_struct *bpfsec = aux->security; + + aux->security =NULL ; +kfree (bpfsec); +} +#endif +static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {
LSM_HOOK_INIT(binder_set_context_mgr,selinux_binder_set_context_mgr),
LSM_HOOK_INIT(binder_transaction,selinux_binder_transaction),security/selinux/hooks.c +8
-0@@ -6471,6 +6572,16 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { LSM_HOOK_INIT(audit_rule_match, selinux_audit_rule_match), LSM_HOOK_INIT(audit_rule_free, selinux_audit_rule_free), #endif + +#ifdef CONFIG_BPF_SYSCALL + LSM_HOOK_INIT(bpf, selinux_bpf), + LSM_HOOK_INIT(bpf_map, selinux_bpf_map), + LSM_HOOK_INIT(bpf_prog, selinux_bpf_prog), + LSM_HOOK_INIT(bpf_map_alloc_security, selinux_bpf_map_alloc), + LSM_HOOK_INIT(bpf_prog_alloc_security, selinux_bpf_prog_alloc), + LSM_HOOK_INIT(bpf_map_free_security,
selinux_bpf_map_free),
+ LSM_HOOK_INIT(bpf_prog_free_security,selinux_bpf_prog_free),security/selinux/hooks.c +1
-0+#endif };static __init int selinux_init (void )security/selinux/include/classmap.h +0
-0security/selinux/include/classmap.h struct security_class_mapping secclass_map[] = · line 242
Quoted 6 lines
security/selinux/include/classmap.h +2
-0@@ -237,6 +237,8 @@ struct security_class_mapping secclass_map[] = { { "access", NULL } }, {"infiniband_endport" , { "manage_subnet", NULL } }, + { "bpf_map", {"create", "read", "write"} }, + { "bpf_prog", {"load", "use"} },Again I have to ask: do you truly need/want two separate classes, or would a single class with distinct permissions suffice, ala:
{ "bpf", { "create_map", "read_map", "write_map","
prog_load",
"prog_use" } },
Quoted 4 lines
Quoted 3 lines
and then allow A self:bpf {
create_mapread_mapwrite_mapprog_loadprog_use}; would be stored in a single policy avtab rule, and be cached in a single AVC entry.
Sorry I missed to reply on this, I keep it that way because sometimes we need to grant the permission of accessing eBPF maps and programs separately. But keep them in a single class definitely works for me.
Quoted 22 lines
I guess for consistency in naming it should be either:
{ "bpf", { "map_create", "map_read", "map_write", "prog_load","
prog_use" } },or:
{ "bpf", { "create_map", "read_map", "write_map", "load_prog","
use_prog" } },Quoted 12 lines
Quoted 12 lines
security/selinux/include/classmap.h +0
-0{ NULL } };security/selinux/include/objsec.h +0
-0@@ -150,6 +150,10 @@ struct pkey_security_struct {u32 sid;/* SID of pkey */ };
Quoted 7 lines
Quoted 7 lines
security/selinux/include/objsec.h struct pkey_security_struct { · line 159
Quoted 7 lines
security/selinux/include/objsec.h +4
-0+struct bpf_security_struct { +u32 sid;/*SID of bpf obj creater*/ +}; +extern unsigned int selinux_checkreqprot;#endif /* _SELINUX_OBJSEC_H_ */
--
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
Re: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
Quoted 201 lines · Chenbo Feng via Selinux
Quoted 199 lines · Stephen Smalley
Quoted 198 lines · Stephen Smalley
Quoted 182 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Implement the actual checks introduced to eBPF related syscalls.
This
implementation use the security field inside bpf object to store a
sid that
identify the bpf object. And when processes try to access the object,
selinux will check if processes have the right privileges. The creation
of eBPF object are also checked at the general bpf check hook and
new
cmd introduced to eBPF domain can also be checked there.Signed-off-by Chenbo Feng <[email protected]>---
?security/selinux/hooks.c????????????| 111
++++++++++++++++++++++++++++++++++++
?security/selinux/include/classmap.h |???2 +
?security/selinux/include/objsec.h???|???4 ++
?3 files changed, 117 insertions(+)security/selinux/hooks.c +0
-0@@ -85,6 +85,7 @@?#include <
linux/export.h>
?#include <linux/msg.h>
?#include <linux/shm.h>
+#include <linux/bpf.h>?#include "
avc.h"
?#include "objsec.h"security/selinux/hooks.c +0
-0@@ -6252,6 +6253,106 @@ static voidselinux_ib_free_security(void
*ib_sec)
?}
?#endifsecurity/selinux/hooks.c +10
-0+#ifdef CONFIG_BPF_SYSCALL +static int selinux_bpf (int cmd,union bpf_attr *attr, +????????????????????????????????unsigned int size) +{ +???u32 sid = current_sid(); +???int ret; + +???switch (cmd) { +???case BPF_MAP_CREATE: +???????????ret = avc_has_perm(sid, sid, SECCLASS_BPF_MAP,
BPF_MAP__CREATE, +??????????????????????????????NULL); +???????????break;
+???caseBPF_PROG_LOAD:
+???????????ret =avc_has_perm(sid, sid, SECCLASS_BPF_PROG, BPF_PROG__LOAD, +??????????????????????????????NULL); +???????????break;
+???default:
+???????????ret = 0;
+???????????break;
+???}security/selinux/hooks.c +80
-0+ +???return ret; +} + +static u32 bpf_map_fmode_to_av (fmode_t fmode) +{ +???u32 av = 0; + +???if (f_mode & FMODE_READ) +???????????av |= BPF_MAP__READ; +???if (f_mode & FMODE_WRITE) +???????????av |= BPF_MAP__WRITE; +???return av; +} + +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) +{ +???u32 sid = current_sid(); +???struct bpf_security_struct *bpfsec; + +???bpfsec = map->security; +???return avc_has_perm(sid, bpfsec->sid, SECCLASS_BPF_MAP, +???????????????????????bpf_map_fmode_to_av(fmode), NULL); +} + +static int selinux_bpf_prog (struct bpf_prog *prog) +{ +???u32 sid = current_sid(); +???struct bpf_security_struct *bpfsec; + +???bpfsec = prog->aux->security; +???return avc_has_perm(sid, bpfsec->sid, SECCLASS_BPF_PROG, +???????????????????????BPF_PROG__USE, NULL); +} + +static int selinux_bpf_map_alloc (struct bpf_map *map) +{ +???struct bpf_security_struct *bpfsec; + +???bpfsec = kzalloc(sizeof(*bpfsec), GFP_KERNEL); +???if (!bpfsec) +???????????return -ENOMEM; + +???bpfsec->sid = current_sid(); +???map->security = bpfsec; + +???return 0; +} + +static void selinux_bpf_map_free (struct bpf_map *map) +{ +???struct bpf_security_struct *bpfsec = map->security; + +???map->security = NULL; +???kfree(bpfsec); +} + +static int selinux_bpf_prog_alloc (struct bpf_prog_aux *aux) +{ +???struct bpf_security_struct *bpfsec; + +???bpfsec = kzalloc(sizeof(*bpfsec), GFP_KERNEL); +???if (!bpfsec) +???????????return -ENOMEM; + +???bpfsec->sid = current_sid(); +???aux->security = bpfsec; + +???return 0; +} + +static void selinux_bpf_prog_free (struct bpf_prog_aux *aux) +{ +???struct bpf_security_struct *bpfsec = aux->security; + +???aux->security = NULL; +???kfree(bpfsec); +} +#endif +?static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {
????LSM_HOOK_INIT(binder_set_context_mgr,selinux_binder_set_context_mgr),
????LSM_HOOK_INIT(binder_transaction,selinux_binder_transaction),security/selinux/hooks.c +0
-0@@ -6471,6 +6572,16 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { ????LSM_HOOK_INIT(audit_rule_match, selinux_audit_rule_match), ????LSM_HOOK_INIT(audit_rule_free, selinux_audit_rule_free),?#endif
security/selinux/hooks.c +6
-0+ +#ifdef CONFIG_BPF_SYSCALL +???LSM_HOOK_INIT(bpf, selinux_bpf), +???LSM_HOOK_INIT(bpf_map, selinux_bpf_map), +???LSM_HOOK_INIT(bpf_prog, selinux_bpf_prog), +???LSM_HOOK_INIT(bpf_map_alloc_security,
selinux_bpf_map_alloc),
+???LSM_HOOK_INIT(bpf_prog_alloc_security,selinux_bpf_prog_alloc),
+???LSM_HOOK_INIT(bpf_map_free_security,selinux_bpf_map_free),
+???LSM_HOOK_INIT(bpf_prog_free_security,selinux_bpf_prog_free),
+#endif
?};?static
__initintselinux_init(void)security/selinux/include/classmap.h +0
-0@@ -237,6 +237,8 @@ struct security_class_mappingQuoted 7 lines
secclass_map[] =
{
??????{ "access", NULL } },
????{ "infiniband_endport",
??????{ "manage_subnet", NULL } },
+???{ "bpf_map", {"create", "read", "write"} },
+???{ "bpf_prog", {"load", "use"} },Again I have to ask: do you truly need/want two separate classes, or
would a single class with distinct permissions suffice, ala:
????????{ "bpf", { "create_map", "read_map", "write_map", "prog_load",
"prog_use" } },
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
and then allow A self:bpf {
create_mapread_mapwrite_mapprog_loadprog_use}; would be stored in a single policy avtab rule, and be cached in a single AVC entry.Sorry I missed to reply on this, I keep it that way because sometimes we need to grant the permission of accessing eBPF maps and programs separately. But keep them in a single class definitely works for me.
If we anticipated a large number of permissions being defined for either bpf maps or programs, or if we were labeling them differently (e.g. inheriting from creator for one, while using type transitions for another), then it might make more sense to split the class (so that we can support up to 32 distinct permissions for each one, or because we'd never end up allowing both map and prog permissions to the same target SID/context). But in this case I can't see any benefit to using two classes, and it would consume more memory to do so.
BTW, please be sure to cc Paul Moore on these patches if you aren't already since he is the selinux kernel tree maintainer.
Quoted 24 lines
Quoted 24 lines
I guess for consistency in naming it should be either:
????????{ "bpf", { "map_create", "map_read", "map_write", "prog_load",
"prog_use" } },or:
????????{ "bpf", { "
create_map", "read_map", "write_map", "load_prog",
"use_prog" } },Quoted 12 lines
Quoted 12 lines
????{ NULL }
???};security/selinux/include/objsec.h +0
-0@@ -150,6 +150,10 @@ struct pkey_security_struct {????u32?????sid;????/* SID of pkey */
?};
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
security/selinux/include/objsec.h +4
-0+struct bpf_security_struct { +???u32 sid;??/*SID of bpf obj creater*/ +}; +?extern unsigned int
selinux_checkreqprot;?#endif /* _SELINUX_OBJSEC_H_ */
--
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
kbuild test robot
build botRe: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
In reply to Chenbo Fengurl: https://github.com/0day-ci/linux/commits/Chenbo-Feng/bpf-security-New-file-mode-and-LSM-hooks-for-eBPF-object-permission-control/20171011-010349 config: xtensa-allyesconfig (attached as…
Hi Chenbo,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Chenbo-Feng/bpf-security-New-file-mode-and-LSM-hooks-for-eBPF-object-permission-control/20171011-010349
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
security//selinux/hooks.c: In function 'bpf_map_fmode_to_av':
>> security//selinux/hooks.c:6284:6: error: 'f_mode' undeclared (first use in this function)
if (f_mode & FMODE_READ)
^
security//selinux/hooks.c:6284:6: note: each undeclared identifier is reported only once for each function it appears in
vim +/f_mode +6284 security//selinux/hooks.c
6279
6280 static u32 bpf_map_fmode_to_av(fmode_t fmode)
6281 {
6282 u32 av = 0;
6283
> 6284 if (f_mode & FMODE_READ)
6285 av |= BPF_MAP__READ;
6286 if (f_mode & FMODE_WRITE)
6287 av |= BPF_MAP__WRITE;
6288 return av;
6289 }
6290
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
kbuild test robot
build botRe: [PATCH net-next v2 4/5] selinux: bpf: Add selinux check for eBPF syscall operations
In reply to Chenbo Fengurl: https://github.com/0day-ci/linux/commits/Chenbo-Feng/bpf-security-New-file-mode-and-LSM-hooks-for-eBPF-object-permission-control/20171011-010349 config: x86_64-randconfig-u0-10110310 (attached…
Hi Chenbo,
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Chenbo-Feng/bpf-security-New-file-mode-and-LSM-hooks-for-eBPF-object-permission-control/20171011-010349
config: x86_64-randconfig-u0-10110310 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64 All warnings (new ones prefixed by >>):
In file included from include/linux/init.h:4:0,
from security/selinux/hooks.c:27:
security/selinux/hooks.c: In function 'bpf_map_fmode_to_av':
security/selinux/hooks.c:6284:6: error: 'f_mode' undeclared (first use in this function)
if (f_mode & FMODE_READ)
^
include/linux/compiler.h:156:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> security/selinux/hooks.c:6284:2: note: in expansion of macro 'if'
if (f_mode & FMODE_READ)
^~
security/selinux/hooks.c:6284:6: note: each undeclared identifier is reported only once for each function it appears in
if (f_mode & FMODE_READ)
^
include/linux/compiler.h:156:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> security/selinux/hooks.c:6284:2: note: in expansion of macro 'if' if (f_mode & FMODE_READ)
^~
vim +/if +6284 security/selinux/hooks.c
6279
6280 static u32 bpf_map_fmode_to_av(fmode_t fmode)
6281 {
6282 u32 av = 0;
6283
> 6284 if (f_mode & FMODE_READ)
6285 av |= BPF_MAP__READ;
6286 if (f_mode & FMODE_WRITE)
6287 av |= BPF_MAP__WRITE;
6288 return av;
6289 }
6290
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
PATCH v2 5/5 selinux: bpf: Add addtional check for bpf object file receive
In reply to Chenbo FengFrom: Chenbo Feng <[email protected]>
Introduce a bpf object related check when sending and receiving files through unix domain socket as well as binder. It checks if the receiving process have privilege to read/write the bpf map or use the bpf program. This check is necessary because the bpf maps and programs are using a anonymous inode as their shared inode so the normal way of checking the files and sockets when passing between processes cannot work properly on eBPF object. This check only works when the BPF_SYSCALL is configured. The information stored inside the file security struct is the same as the information in bpf object security struct.
--- include/linux/bpf.h | 3 +++ include/linux/lsm_hooks.h | 17 +++++++++++++ include/linux/security.h | 9 +++++++ kernel/bpf/syscall.c | 4 ++-- security/security.c | 8 +++++++ security/selinux/hooks.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++ 6 files changed, 100 insertions(+), 2 deletions(-)
include/linux/bpf.h +3 -0
@@ -285,6 +285,9 @@ int bpf_prog_array_copy_to_user(struct bpf_prog_array __rcu *progs,#ifdef CONFIG_BPF_SYSCALL DECLARE_PER_CPU (int, bpf_prog_active); +extern const struct file_operations bpf_map_fops; +extern const struct file_operations bpf_prog_fops; +#define BPF_PROG_TYPE (_id, _ops) \ extern const struct bpf_verifier_ops _ops;#define BPF_MAP_TYPE (_id, _ops) \
include/linux/lsm_hooks.h +17 -0
@@ -1385,6 +1385,19 @@* @bpf_prog_free_security: * Clean up the security information stored inside bpf prog. * +* @bpf_map_file: +* When creating a bpf map fd, set up the file security information with +* the bpf security information stored in the map struct. So when the map +* fd is passed between processes, the security module can directly read +* the security information from file security struct rather than the bpf +* security struct. +* +* @bpf_prog_file: +* When creating a bpf prog fd, set up the file security information with +* the bpf security information stored in the prog struct. So when the prog +* fd is passed between processes, the security module can directly read +* the security information from file security struct rather than the bpf +* security struct. */ union security_list_options {int (*binder_set_context_mgr)(struct task_struct *mgr);
@@ -1726,6 +1739,8 @@ union security_list_options {void (*bpf_map_free_security)(struct bpf_map *map);int (*bpf_prog_alloc_security)(struct bpf_prog_aux *aux);void (*bpf_prog_free_security)(struct bpf_prog_aux *aux); +void (*bpf_map_file)(struct bpf_map *map,struct file *file); +void (*bpf_prog_file)(struct bpf_prog_aux *aux,struct file *file);#endif /* CONFIG_BPF_SYSCALL */ };
@@ -1954,6 +1969,8 @@ struct security_hook_heads {struct list_head bpf_map_free_security;struct list_head bpf_prog_alloc_security;struct list_head bpf_prog_free_security; +struct list_head bpf_map_file; +struct list_head bpf_prog_file;#endif /* CONFIG_BPF_SYSCALL */ } __randomize_layout;
include/linux/security.h +9 -0
@@ -1740,6 +1740,8 @@ extern int security_bpf_map_alloc(struct bpf_map *map);extern void security_bpf_map_free (struct bpf_map *map);extern int security_bpf_prog_alloc (struct bpf_prog_aux *aux);extern void security_bpf_prog_free (struct bpf_prog_aux *aux); +extern void security_bpf_map_file (struct bpf_map *map,struct file *file); +extern void security_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file);#else static inline int security_bpf (int cmd,union bpf_attr *attr,unsigned int size)
@@ -1772,6 +1774,13 @@ static inline int security_bpf_prog_alloc(struct bpf_prog_aux *aux)static inline void security_bpf_prog_free (struct bpf_prog_aux *aux) { } + +static inline void security_bpf_map_file (struct bpf_map *map,struct file *file) +{ } + +static inline void security_bpf_prog_file (struct bpf_prog_aux *aux, +struct file *file) +{ }#endif /* CONFIG_SECURITY */ #endif /* CONFIG_BPF_SYSCALL */
kernel/bpf/syscall.c +2 -2
@@ -313,7 +313,7 @@ static ssize_t bpf_dummy_write(struct file *filp, const char __user *buf,return -EINVAL ; } -static const struct file_operations bpf_map_fops = { +const struct file_operations bpf_map_fops = { #ifdef CONFIG_PROC_FS .show_fdinfo = bpf_map_show_fdinfo, #endif
@@ -964,7 +964,7 @@ static void bpf_prog_show_fdinfo(struct seq_file *m, struct file *filp) }#endif -static const struct file_operations bpf_prog_fops = { +const struct file_operations bpf_prog_fops = { #ifdef CONFIG_PROC_FS .show_fdinfo = bpf_prog_show_fdinfo, #endif
security/security.c +8 -0
@@ -1734,4 +1734,12 @@ void security_bpf_prog_free(struct bpf_prog_aux *aux) {call_void_hook (bpf_prog_free_security, aux); } +void security_bpf_map_file (struct bpf_map *map,struct file *file) +{ +call_void_hook (bpf_map_file, map, file); +} +void security_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file) +{ +call_void_hook (bpf_prog_file, aux, file); +}#endif /* CONFIG_BPF_SYSCALL */
security/selinux/hooks.c +61 -0
97 lines not on this page · raw message
Signature · 6 lines
2.14.2.920.gcf0c67979c-goog -- 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
Re: [PATCH net-next v2 5/5] selinux: bpf: Add addtional check for bpf object file receive
Quoted 268 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce a bpf object related check when sending and receiving files through unix domain socket as well as binder. It checks if the receiving
process have privilege to read/write the bpf map or use the bpf program.
This check is necessary because the bpf maps and programs are using a anonymous inode as their shared inode so the normal way of checking the
files and sockets when passing between processes cannot work properly on
eBPF object. This check only works when theBPF_SYSCALLis configured.
The information stored inside the file security struct is the same as the information in bpf object security struct.Signed-off-by Chenbo Feng <[email protected]>---
include/linux/bpf.h | 3 +++
include/linux/lsm_hooks.h | 17 +++++++++++++
include/linux/security.h | 9 +++++++
kernel/bpf/syscall.c | 4 ++--
security/security.c | 8 +++++++
security/selinux/hooks.c | 61
+++++++++++++++++++++++++++++++++++++++++++++++6 files changed, 100 insertions(+), 2 deletions(-)include/linux/bpf.h +0
-0@@ -285,6 +285,9 @@ int bpf_prog_array_copy_to_user(structbpf_prog_array __rcu *progs, #ifdef CONFIG_BPF_SYSCALL DECLARE_PER_CPU(int, bpf_prog_active);include/linux/bpf.h +3
-0+extern const struct file_operations bpf_map_fops; +extern const struct file_operations bpf_prog_fops; +#define
BPF_PROG_TYPE(_id, _ops)\
extern const structbpf_verifier_ops_ops; #defineBPF_MAP_TYPE(_id, _ops)\include/linux/lsm_hooks.h +2
-0@@ -1385,6 +1385,19 @@ * @bpf_prog_free_security: * Clean up the security information stored inside bpf prog. * + * @bpf_map_file: + * When creating a bpf map fd, set up the file securityinformation with
+ * the bpf security information stored in the map struct. So
when the map
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
+ *
+ * @bpf_prog_file:
+ * When creating a bpf prog fd, set up the file security
information with
+ * the bpf security information stored in the prog struct. So
when the prog
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
*/
unionsecurity_list_options{
int (*binder_set_context_mgr)(structtask_struct*mgr);include/linux/lsm_hooks.h +2
-0@@ -1726,6 +1739,8 @@ union security_list_options { void (*bpf_map_free_security)(struct bpf_map *map); int (*bpf_prog_alloc_security)(struct bpf_prog_aux *aux); void (*bpf_prog_free_security)(struct bpf_prog_aux *aux); +void (*bpf_map_file)(struct bpf_map *map,struct file *file); +void (*bpf_prog_file)(struct bpf_prog_aux *aux,struct file *file); #endif /* CONFIG_BPF_SYSCALL */};
include/linux/lsm_hooks.h +2
-0@@ -1954,6 +1969,8 @@ struct security_hook_heads { struct list_head bpf_map_free_security; struct list_head bpf_prog_alloc_security; struct list_head bpf_prog_free_security; +struct list_head bpf_map_file; +struct list_head bpf_prog_file; #endif /* CONFIG_BPF_SYSCALL */ } __randomize_layout;include/linux/security.h +2
-0@@ -1740,6 +1740,8 @@ extern int security_bpf_map_alloc(struct bpf_map *map); extern void security_bpf_map_free(struct bpf_map *map); extern int security_bpf_prog_alloc(struct bpf_prog_aux *aux); extern void security_bpf_prog_free(struct bpf_prog_aux *aux); +extern void security_bpf_map_file (struct bpf_map *map,struct file *file); +extern void security_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file);#else
static inline intsecurity_bpf(int cmd, union bpf_attr *attr, unsigned int size)include/linux/security.h +0
-0@@ -1772,6 +1774,13 @@ static inline int security_bpf_prog_alloc(struct bpf_prog_aux *aux)
static inline voidsecurity_bpf_prog_free(struct bpf_prog_aux *aux){ }include/linux/security.h +2
-0+ +static inline void security_bpf_map_file(struct bpf_map *map, structfile *file)
include/linux/security.h +5
-0+{ } + +static inline void security_bpf_prog_file (struct bpf_prog_aux *aux, + struct file *file) +{ }#endif /*
CONFIG_SECURITY*/
#endif /*CONFIG_BPF_SYSCALL*/kernel/bpf/syscall.c +0
-0@@ -313,7 +313,7 @@ static ssize_t bpf_dummy_write(struct file *filp,const char __user *buf, return -EINVAL; }kernel/bpf/syscall.c +1
-1-static const struct file_operations bpf_map_fops = { +const struct file_operations bpf_map_fops = {#ifdef
CONFIG_PROC_FS
.show_fdinfo =bpf_map_show_fdinfo,
#endifkernel/bpf/syscall.c +0
-0@@ -964,7 +964,7 @@ static void bpf_prog_show_fdinfo(struct seq_file *m, struct file *filp) } #endifkernel/bpf/syscall.c +1
-1-static const struct file_operations bpf_prog_fops = { +const struct file_operations bpf_prog_fops = {#ifdef
CONFIG_PROC_FS
.show_fdinfo =bpf_prog_show_fdinfo,
#endifsecurity/security.c +5
-0@@ -1734,4 +1734,12 @@ void security_bpf_prog_free(struct bpf_prog_aux *aux) { call_void_hook(bpf_prog_free_security, aux); } +void security_bpf_map_file (struct bpf_map *map,struct file *file) +{ +call_void_hook (bpf_map_file, map, file); +} +void security_bpf_prog_file(struct bpf_prog_aux *aux, struct file*file)
security/security.c +3
-0+{ +call_void_hook (bpf_prog_file, aux, file); +}#endif /*
CONFIG_BPF_SYSCALL*/security/selinux/hooks.c +0
-0@@ -1815,6 +1815,10 @@ static inline int file_path_has_perm(conststruct cred *cred, return inode_has_perm(cred, file_inode(file), av, &ad); }security/selinux/hooks.c +4
-0+#ifdef CONFIG_BPF_SYSCALL +static int bpf_file_check (struct file *file,u32 sid); +#endif +/* Check whether a task can use an open file descriptor to access an inode in a given way. Check access to the descriptor itself, and then use
dentry_has_permtosecurity/selinux/hooks.c +0
-0@@ -1845,6 +1849,12 @@ static int file_has_perm(const struct cred *cred, goto out; }security/selinux/hooks.c +6
-0+#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file,cred_sid (cred)); +if (rc) + goto out; +#endif +/* av is zero if only checking access to the descriptor. */ rc = 0;
if (av)security/selinux/hooks.c +0
-0@@ -2165,6 +2175,12 @@ static int selinux_binder_transfer_file(structtask_struct *from, return rc; }security/selinux/hooks.c +6
-0+#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file, sid); +if (rc) +return rc; +#endif +if (unlikely(IS_PRIVATE(d_backing_inode(dentry)))) return 0;
security/selinux/hooks.c +0
-0@@ -6288,6 +6304,33 @@ static u32 bpf_map_fmode_to_av(fmode_t fmode) return av; }
+/* This function will check the file pass through unix socket or binder to see
+ * if it is a bpf related object. And apply correspinding checks on the bpf
+ * object based on the type. The bpf maps and programs, not like other files and
+ * socket, are using a shared anonymous inode inside the kernel as their inode.
+ * So checking that inode cannot identify if the process have privilege to
+ * access the bpf object and that's why we have to add this additional check in
+ *selinux_file_receiveandselinux_binder_transfer_files.
+ */security/selinux/hooks.c +8
-0+static int bpf_file_check (struct file *file,u32 sid) +{ +struct file_security_struct *fsec = file->f_security; +int ret; + +if (file->f_op == &bpf_map_fops) { + ret = avc_has_perm(sid, fsec->sid, SECCLASS_BPF_MAP, + bpf_map_fmode_to_av(file-Quoted 1 line
f_mode), NULL);security/selinux/hooks.c +4
-0+if (ret) +return ret; + }else if (file->f_op == &bpf_prog_fops) { + ret = avc_has_perm(sid, fsec->sid,
SECCLASS_BPF_PROG,security/selinux/hooks.c +7
-0+ BPF_PROG__USE, NULL); +if (ret) +return ret; + } +return 0 ; +} +static int
selinux_bpf_map(struct bpf_map *map, fmode_t fmode){
u32 sid =current_sid();security/selinux/hooks.c +6
-0@@ -6351,6 +6394,22 @@ static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) aux->security = NULL; kfree(bpfsec); } + +static void selinux_bpf_map_file (struct bpf_map *map,struct file *file) +{ +struct bpf_security_struct *bpfsec = map->security; +struct file_security_struct *fsec = file->f_security; +
security/selinux/hooks.c static void selinux_bpf_prog_free(struct · line 6414
Quoted 10 lines
security/selinux/hooks.c +9
-0+ fsec->sid = bpfsec->sid; +} + +static void selinux_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file) +{ +struct bpf_security_struct *bpfsec = aux->security; +struct file_security_struct *fsec = file->f_security; + + fsec->sid = bpfsec->sid;
I could be wrong, but isn't it the case that fsec->sid already will equal bpfsec->sid, because they are both created by the same thread during the same system call, and they each inherit the SID of the current task?
What I expected you to do was to add and set a flags field in the file_security_struct to indicate that this is a bpf map or prog, and then test for that in your bpf_file_check() function instead of having to export and test the fops structures.
Quoted 17 lines
security/selinux/hooks.c +1
-0+}#endif
static structsecurity_hook_listselinux_hooks[]__lsm_ro_after_init= {security/selinux/hooks.c +2
-0@@ -6581,6 +6640,8 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { LSM_HOOK_INIT(bpf_prog_alloc_security, selinux_bpf_prog_alloc), LSM_HOOK_INIT(bpf_map_free_security, selinux_bpf_map_free), LSM_HOOK_INIT(bpf_prog_free_security, selinux_bpf_prog_free), + LSM_HOOK_INIT(bpf_map_file, selinux_bpf_map_file), + LSM_HOOK_INIT(bpf_prog_file, selinux_bpf_prog_file),#endif
};
Re: [PATCH net-next v2 5/5] selinux: bpf: Add addtional check for bpf object file receive
Quoted 276 lines · Stephen Smalley
Quoted 275 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce a bpf object related check when sending and receiving files through unix domain socket as well as binder. It checks if the receiving
process have privilege to read/write the bpf map or use the bpf program.
This check is necessary because the bpf maps and programs are using a anonymous inode as their shared inode so the normal way of checking the
files and sockets when passing between processes cannot work properly on
eBPF object. This check only works when theBPF_SYSCALLis configured.
The information stored inside the file security struct is the same as the information in bpf object security struct.Signed-off-by Chenbo Feng <[email protected]>--- include/linux/bpf.h | 3 +++ include/linux/lsm_hooks.h | 17 +++++++++++++ include/linux/security.h | 9 +++++++ kernel/bpf/syscall.c | 4 ++-- security/security.c | 8 +++++++ security/selinux/hooks.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++ 6 files changed, 100 insertions(+), 2 deletions(-)include/linux/bpf.h +3
-0@@ -285,6 +285,9 @@ int bpf_prog_array_copy_to_user(struct bpf_prog_array __rcu *progs,#ifdef CONFIG_BPF_SYSCALL DECLARE_PER_CPU (int, bpf_prog_active); +extern const struct file_operations bpf_map_fops; +extern const struct file_operations bpf_prog_fops; +#define BPF_PROG_TYPE (_id, _ops) \ extern const struct bpf_verifier_ops _ops;#define
BPF_MAP_TYPE(_id, _ops)\include/linux/lsm_hooks.h +2
-0@@ -1385,6 +1385,19 @@* @bpf_prog_free_security: * Clean up the security information stored inside bpf prog. * +* @bpf_map_file: +* When creating a bpf map fd, set up the file security information with
+ * the bpf security information stored in the map struct. So
when the map
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
+ *
+ * @bpf_prog_file:
+ * When creating a bpf prog fd, set up the file security
information with
+ * the bpf security information stored in the prog struct. So
when the prog
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
*/union security_list_options { int (*binder_set_context_mgr)(struct task_struct *mgr);include/linux/lsm_hooks.h +2
-0@@ -1726,6 +1739,8 @@ union security_list_options {void (*bpf_map_free_security)(struct bpf_map *map);int (*bpf_prog_alloc_security)(struct bpf_prog_aux *aux);void (*bpf_prog_free_security)(struct bpf_prog_aux *aux); +void (*bpf_map_file)(struct bpf_map *map,struct file *file); +void (*bpf_prog_file)(struct bpf_prog_aux *aux,struct file *file);#endif /* CONFIG_BPF_SYSCALL */ };
include/linux/lsm_hooks.h +2
-0@@ -1954,6 +1969,8 @@ struct security_hook_heads {struct list_head bpf_map_free_security;struct list_head bpf_prog_alloc_security;struct list_head bpf_prog_free_security; +struct list_head bpf_map_file; +struct list_head bpf_prog_file;#endif /* CONFIG_BPF_SYSCALL */ } __randomize_layout;include/linux/security.h +2
-0@@ -1740,6 +1740,8 @@ extern int security_bpf_map_alloc(struct bpf_map *map);extern void security_bpf_map_free (struct bpf_map *map);extern int security_bpf_prog_alloc (struct bpf_prog_aux *aux);extern void security_bpf_prog_free (struct bpf_prog_aux *aux); +extern void security_bpf_map_file (struct bpf_map *map,struct file *file); +extern void security_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file);#else
static inline int security_bpf(int cmd, unionbpf_attr*attr,
unsigned int size)include/linux/security.h +7
-0@@ -1772,6 +1774,13 @@ static inline int security_bpf_prog_alloc(struct bpf_prog_aux *aux) static inline void security_bpf_prog_free(struct bpf_prog_aux *aux) { } + +static inline void security_bpf_map_file (struct bpf_map *map,struct file *file) +{ } + +static inline void security_bpf_prog_file (struct bpf_prog_aux *aux, +struct file *file) +{ }#endif /* CONFIG_SECURITY */ #endif /*
CONFIG_BPF_SYSCALL*/kernel/bpf/syscall.c +1
-1@@ -313,7 +313,7 @@ static ssize_t bpf_dummy_write(struct file *filp,const char __user *buf, return -EINVAL; } -static const struct file_operations bpf_map_fops = { +const struct file_operations bpf_map_fops = { #ifdef CONFIG_PROC_FS .show_fdinfo = bpf_map_show_fdinfo,#endif
kernel/bpf/syscall.c +1
-1@@ -964,7 +964,7 @@ static void bpf_prog_show_fdinfo(struct seq_file *m, struct file *filp) }#endif -static const struct file_operations bpf_prog_fops = { +const struct file_operations bpf_prog_fops = { #ifdef CONFIG_PROC_FS .show_fdinfo = bpf_prog_show_fdinfo,#endif
security/security.c +5
-0@@ -1734,4 +1734,12 @@ void security_bpf_prog_free(struct bpf_prog_aux *aux) {call_void_hook (bpf_prog_free_security, aux); } +void security_bpf_map_file (struct bpf_map *map,struct file *file) +{ +call_void_hook (bpf_map_file, map, file); +} +void security_bpf_prog_file(struct bpf_prog_aux *aux, struct file*file)
security/security.c +3
-0+{ +call_void_hook (bpf_prog_file, aux, file); +}#endif /* CONFIG_BPF_SYSCALL */ security/selinux/hooks.c +4
-0@@ -1815,6 +1815,10 @@ static inline int file_path_has_perm(conststruct cred *cred, return inode_has_perm(cred, file_inode(file), av, &ad); } +#ifdef CONFIG_BPF_SYSCALL +static int bpf_file_check (struct file *file,u32 sid); +#endif +/* Check whether a task can use an open file descriptor to access an inode in a given way. Check access to the descriptor itself, and then use
dentry_has_permtosecurity/selinux/hooks.c +6
-0@@ -1845,6 +1849,12 @@ static int file_has_perm(const struct cred *cred, goto out; } +#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file,cred_sid (cred)); +if (rc) + goto out; +#endif +/* av is zero if only checking access to the descriptor. */ rc =0 ;if (av)security/selinux/hooks.c +7
-0@@ -2165,6 +2175,12 @@ static int selinux_binder_transfer_file(structtask_struct *from, return rc; } +#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file, sid); +if (rc) +return rc; +#endif +if (unlikely (IS_PRIVATE (d_backing_inode (dentry))))return 0 ;@@ -6288,6 +6304,33 @@ static u32 bpf_map_fmode_to_av(fmode_t fmode)return av; } +/* This function will check the file pass through unix socket or binder to see
+ * if it is a bpf related object. And apply correspinding checks on the bpf
+ * object based on the type. The bpf maps and programs, not like other files and
+ * socket, are using a shared anonymous inode inside the kernel as their inode.
+ * So checking that inode cannot identify if the process have privilege to
+ * access the bpf object and that's why we have to add this additional check in
+ *selinux_file_receiveandselinux_binder_transfer_files.
+ */security/selinux/hooks.c +8
-0+static int bpf_file_check (struct file *file,u32 sid) +{ +struct file_security_struct *fsec = file->f_security; +int ret; + +if (file->f_op == &bpf_map_fops) { + ret = avc_has_perm(sid, fsec->sid, SECCLASS_BPF_MAP, + bpf_map_fmode_to_av(file-Quoted 1 line
f_mode), NULL);security/selinux/hooks.c +4
-0+if (ret) +return ret; + }else if (file->f_op == &bpf_prog_fops) { + ret = avc_has_perm(sid, fsec->sid,
SECCLASS_BPF_PROG,security/selinux/hooks.c +19
-0+ BPF_PROG__USE, NULL); +if (ret) +return ret; + } +return 0 ; +} +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) {u32 sid =current_sid ();@@ -6351,6 +6394,22 @@ static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) aux->security = NULL;kfree (bpfsec); } + +static void selinux_bpf_map_file (struct bpf_map *map,struct file *file) +{ +struct bpf_security_struct *bpfsec = map->security; +struct file_security_struct *fsec = file->f_security; + + fsec->sid = bpfsec->sid; +} + +static void selinux_bpf_prog_file (struct bpf_prog_aux *aux,struct file *file) +{ +struct bpf_security_struct *bpfsec = aux->security;
Quoted 9 lines
security/selinux/hooks.c static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) · line 6403
Quoted 3 lines
security/selinux/hooks.c +3
-0+struct file_security_struct *fsec = file->f_security; + + fsec->sid = bpfsec->sid;I could be wrong, but isn't it the case that
fsec->sidalready will equalbpfsec->sid, because they are both created by the same thread during the same system call, and they each inherit the SID of the current task?
This is true when bpf object is created by the same process that obtains the fd. But there are other ways of getting a bpf object fd from the kernel such as bpf_obj_get and bpf_get_obj_fd_by_id. These action will ask the kernel to allocate a new file for the bpf object and the file sid would be the process ask for fd while the bpfsec->sid is the sid when bpf object get created. These two could be different.
Quoted 9 lines
What I expected you to do was to add and set a flags field in the
file_security_structto indicate that this is a bpf map or prog, and then test for that in yourbpf_file_check()function instead of having to export and test the fops structures.Quoted 3 lines
security/selinux/hooks.c +1
-0+}#endif
Quoted 14 lines
Quoted 11 lines
static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {security/selinux/hooks.c +2
-0@@ -6581,6 +6640,8 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { LSM_HOOK_INIT(bpf_prog_alloc_security, selinux_bpf_prog_alloc), LSM_HOOK_INIT(bpf_map_free_security, selinux_bpf_map_free), LSM_HOOK_INIT(bpf_prog_free_security, selinux_bpf_prog_free), + LSM_HOOK_INIT(bpf_map_file, selinux_bpf_map_file), + LSM_HOOK_INIT(bpf_prog_file, selinux_bpf_prog_file),Quoted 3 lines
#endif
};
--
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
Re: [Non-DoD Source] Re: [PATCH net-next v2 5/5] selinux: bpf: Add addtional check for bpf object file receive
Quoted 311 lines · Chenbo Feng
Quoted 299 lines · Stephen Smalley
Quoted 298 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce a bpf object related check when sending and receiving files
through unix domain socket as well as binder. It checks if the receiving
process have privilege to read/write the bpf map or use the bpf program.
This check is necessary because the bpf maps and programs are using a
anonymous inode as their shared inode so the normal way of checking
the
files and sockets when passing between processes cannot work properly
on
eBPF object. This check only works when theBPF_SYSCALLis configured.
The information stored inside the file security struct is the same as
the information in bpf object security struct.Signed-off-by Chenbo Feng <[email protected]>---
?include/linux/bpf.h???????|??3 +++ ?include/linux/lsm_hooks.h | 17 +++++++++++++ ?include/linux/security.h??|??9 +++++++ ?kernel/bpf/syscall.c??????|??4 ++-- ?security/security.c???????|??8 +++++++ ?security/selinux/hooks.c??| 61+++++++++++++++++++++++++++++++++++++++++++++++
?6 files changed, 100 insertions(+), 2 deletions(-)include/linux/bpf.h +0
-0@@ -285,6 +285,9 @@ int bpf_prog_array_copy_to_user(struct bpf_prog_array __rcu *progs,?#ifdef
CONFIG_BPF_SYSCALL
?DECLARE_PER_CPU(int,bpf_prog_active);include/linux/bpf.h +3
-0+extern const struct file_operations bpf_map_fops; +extern const struct file_operations bpf_prog_fops; +?#define
BPF_PROG_TYPE(_id, _ops)\
??????extern const structbpf_verifier_ops_ops;
?#defineBPF_MAP_TYPE(_id, _ops)\include/linux/lsm_hooks.h +0
-0@@ -1385,6 +1385,19 @@? * @bpf_prog_free_security:
? *???Clean up the security information stored inside bpf prog. ? *
+ * @bpf_map_file:
+ *???When creating a bpf map fd, set up the file security information with
+ *???the bpf security information stored in the map struct. So when the map
+ *???fd is passed between processes, the security module can directly read
+ *???the security information from file security struct rather than the bpf
+ *???security struct.
+ *
+ * @bpf_prog_file:
+ *???When creating a bpf prog fd, set up the file security information with
+ *???the bpf security information stored in the prog struct. So when the prog
+ *???fd is passed between processes, the security module can directly read
+ *???the security information from file security struct rather than the bpf
+ *???security struct.
? */
?unionsecurity_list_options{
??????int (*binder_set_context_mgr)(structtask_struct*mgr);include/linux/lsm_hooks.h +2
-0@@ -1726,6 +1739,8 @@ union security_list_options { ??????void (*bpf_map_free_security)(struct bpf_map *map); ??????int (*bpf_prog_alloc_security)(struct bpf_prog_aux *aux); ??????void (*bpf_prog_free_security)(struct bpf_prog_aux *aux); +?????void (*bpf_map_file)(struct bpf_map *map, struct file *file); +?????void (*bpf_prog_file)(struct bpf_prog_aux *aux, struct file *file);?#endif /*
CONFIG_BPF_SYSCALL*/
?};include/linux/lsm_hooks.h +2
-0@@ -1954,6 +1969,8 @@ struct security_hook_heads { ??????struct list_head bpf_map_free_security; ??????struct list_head bpf_prog_alloc_security; ??????struct list_head bpf_prog_free_security; +?????struct list_head bpf_map_file; +?????struct list_head bpf_prog_file;?#endif /*
CONFIG_BPF_SYSCALL*/
?}__randomize_layout;include/linux/security.h +1
-0@@ -1740,6 +1740,8 @@ extern int security_bpf_map_alloc(struct bpf_map *map); ?extern void security_bpf_map_free(struct bpf_map *map); ?extern int security_bpf_prog_alloc(struct bpf_prog_aux *aux); ?extern void security_bpf_prog_free(struct bpf_prog_aux *aux); +extern void security_bpf_map_file(struct bpf_map *map, structfile
*file);
+extern void security_bpf_prog_file(structbpf_prog_aux*aux, struct
file *file);
?#else
?static inline intsecurity_bpf(int cmd, union bpf_attr *attr, ???????????????????????????????????????????unsigned int size)include/linux/security.h +0
-0@@ -1772,6 +1774,13 @@ static inline int security_bpf_prog_alloc(struct bpf_prog_aux *aux)?static inline void
security_bpf_prog_free(struct bpf_prog_aux *aux)
?{ }include/linux/security.h +2
-0+ +static inline void security_bpf_map_file(struct bpf_map *map,struct
file *file)include/linux/security.h +3
-0+{ } + +static inline void security_bpf_prog_file(struct bpf_prog_aux*aux, +???????????????????????????????????????struct file *file) +{ }
?#endif /*CONFIG_SECURITY*/
?#endif /*CONFIG_BPF_SYSCALL*/kernel/bpf/syscall.c +1
-1@@ -313,7 +313,7 @@ static ssize_t bpf_dummy_write(struct file *filp, const char __user *buf, ??????return -EINVAL; ?} -static const struct file_operations bpf_map_fops = { +const struct file_operations bpf_map_fops = {?#ifdef
CONFIG_PROC_FS
??????.show_fdinfo????=bpf_map_show_fdinfo,
?#endifkernel/bpf/syscall.c +0
-0@@ -964,7 +964,7 @@ static void bpf_prog_show_fdinfo(struct
seq_file
*m, struct file *filp)
?}
?#endifkernel/bpf/syscall.c +1
-1-static const struct file_operations bpf_prog_fops = { +const struct file_operations bpf_prog_fops = {?#ifdef
CONFIG_PROC_FS
??????.show_fdinfo????=bpf_prog_show_fdinfo,
?#endifsecurity/security.c +1
-0@@ -1734,4 +1734,12 @@ void security_bpf_prog_free(struct bpf_prog_aux *aux) ?{ ??????call_void_hook(bpf_prog_free_security, aux); ?} +void security_bpf_map_file(struct bpf_map *map, struct file*file)
security/security.c +4
-0+{ +?????call_void_hook(bpf_map_file, map, file); +} +void security_bpf_prog_file(struct bpf_prog_aux *aux, structfile
*file)security/security.c +3
-0+{ +?????call_void_hook(bpf_prog_file, aux, file); +}?#endif /*
CONFIG_BPF_SYSCALL*/security/selinux/hooks.c +4
-0@@ -1815,6 +1815,10 @@ static inline int file_path_has_perm(conststruct cred *cred, ??????return inode_has_perm(cred, file_inode(file), av, &ad); ?} +#ifdef CONFIG_BPF_SYSCALL +static int bpf_file_check (struct file *file,u32 sid); +#endif +?/* Check whether a task can use an open file descriptor to ????access an inode in a given way.??Check access to the ????descriptor itself, and then use
dentry_has_permtosecurity/selinux/hooks.c +6
-0@@ -1845,6 +1849,12 @@ static int file_has_perm(const struct cred *cred, ??????????????????????goto out; ??????} +#ifdef CONFIG_BPF_SYSCALL +?????rc = bpf_file_check(file, cred_sid(cred)); +?????if (rc) +?????????????goto out; +#endif +??????/* av is zero if only checking access to the descriptor. */ ??????rc = 0;
??????if (av)security/selinux/hooks.c +0
-0@@ -2165,6 +2175,12 @@ static intselinux_binder_transfer_file(struct
task_struct*from,
??????????????????????return rc;
??????}security/selinux/hooks.c +6
-0+#ifdef CONFIG_BPF_SYSCALL +?????rc = bpf_file_check(file, sid); +?????if (rc) +?????????????return rc; +#endif +??????if (unlikely(IS_PRIVATE(d_backing_inode(dentry)))) ??????????????return 0;
security/selinux/hooks.c +1
-0@@ -6288,6 +6304,33 @@ static u32 bpf_map_fmode_to_av(fmode_t fmode) ??????return av; ?} +/* This function will check the file pass through unix socket or binder to see
+ * if it is a bpf related object. And apply correspinding checks on
the bpf
+ * object based on the type. The bpf maps and programs, not like other files and
+ * socket, are using a shared anonymous inode inside the kernel as
their inode.
+ * So checking that inode cannot identify if the process have privilege to
+ * access the bpf object and that's why we have to add this additional check in
+ *selinux_file_receiveandselinux_binder_transfer_files.
+ */security/selinux/hooks.c +7
-0+static int bpf_file_check (struct file *file,u32 sid) +{ +?????struct file_security_struct *fsec = file->f_security; +?????int ret; + +?????if (file->f_op == &bpf_map_fops) { +?????????????ret = avc_has_perm(sid, fsec->sid,
SECCLASS_BPF_MAP, +????????????????????????????????bpf_map_fmode_to_av(file-Quoted 1 line
f_mode), NULL);+?????????????if (ret) +?????????????????????return ret;
+?????} else if (file->f_op==&bpf_prog_fops) { +?????????????ret =avc_has_perm(sid, fsec->sid, SECCLASS_BPF_PROG, +????????????????????????????????BPF_PROG__USE, NULL); +?????????????if (ret) +?????????????????????return ret;
+?????}
+?????return 0;security/selinux/hooks.c +2
-0+} +?static int
selinux_bpf_map(struct bpf_map *map, fmode_t fmode)?{
??????u32 sid =current_sid();security/selinux/hooks.c +2
-0@@ -6351,6 +6394,22 @@ static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) ??????aux->security = NULL; ??????kfree(bpfsec); ?} + +static void selinux_bpf_map_file(struct bpf_map *map, structfile
*file)security/selinux/hooks.c +8
-0+{ +?????struct bpf_security_struct *bpfsec = map->security; +?????struct file_security_struct *fsec = file->f_security; + +?????fsec->sid = bpfsec->sid; +} + +static void selinux_bpf_prog_file(struct bpf_prog_aux *aux,struct
file *file)
+{
+?????structbpf_security_struct*bpfsec =aux->security;Quoted 9 lines
Quoted 3 lines
+?????struct
file_security_struct*fsec =file->f_security; +
+?????fsec->sid =bpfsec->sid;I could be wrong, but isn't it the case that
fsec->sidalready will equalbpfsec->sid, because they are both created by the same thread during the same system call, and they each inherit the SID of the current task?
Quoted 7 lines
This is true when bpf object is created by the same process that obtains the fd. But there are other ways of getting a bpf object fd from the kernel such as
bpf_obj_getandbpf_get_obj_fd_by_id. These action will ask the kernel to allocate a new file for the bpf object and the file sid would be the process ask for fd while the bpfsec-Quoted 1 line
sid
is the sid when bpf object get created. These two could be different.
Oh, in that case you shouldn't change the fsec->sid; you'll need to use the bpfsec->sid in your checks instead. But you can still do what I described below.
Quoted 11 lines
Quoted 11 lines
What I expected you to do was to add and set a flags field in the
file_security_structto indicate that this is a bpf map or prog, and
then test for that in yourbpf_file_check()function instead of having
to export and test the fops structures.Quoted 3 lines
+}
?#endif
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
?static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {security/selinux/hooks.c +0
-0@@ -6581,6 +6640,8 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { ??????LSM_HOOK_INIT(bpf_prog_alloc_security, selinux_bpf_prog_alloc),Quoted 8 lines
Quoted 8 lines
security/selinux/hooks.c +2
-0??????LSM_HOOK_INIT(bpf_map_free_security, selinux_bpf_map_free), ??????LSM_HOOK_INIT(bpf_prog_free_security, selinux_bpf_prog_free), +?????LSM_HOOK_INIT(bpf_map_file, selinux_bpf_map_file), +?????LSM_HOOK_INIT(bpf_prog_file, selinux_bpf_prog_file),?#endif
?};
--
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
Re: [Non-DoD Source] Re: [PATCH net-next v2 5/5] selinux: bpf: Add addtional check for bpf object file receive
Quoted 317 lines · Stephen Smalley
Quoted 316 lines · Chenbo Feng
Quoted 299 lines · Stephen Smalley
Quoted 298 lines · Chenbo Feng
From: Chenbo Feng <[email protected]>
Introduce a bpf object related check when sending and receiving files
through unix domain socket as well as binder. It checks if the receiving
process have privilege to read/write the bpf map or use the bpf program.
This check is necessary because the bpf maps and programs are using a
anonymous inode as their shared inode so the normal way of checking
the
files and sockets when passing between processes cannot work properly
on
eBPF object. This check only works when theBPF_SYSCALLis configured.
The information stored inside the file security struct is the same as
the information in bpf object security struct.Signed-off-by Chenbo Feng <[email protected]>--- include/linux/bpf.h | 3 +++ include/linux/lsm_hooks.h | 17 +++++++++++++ include/linux/security.h | 9 +++++++ kernel/bpf/syscall.c | 4 ++-- security/security.c | 8 +++++++ security/selinux/hooks.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++ 6 files changed, 100 insertions(+), 2 deletions(-)include/linux/bpf.h +3
-0@@ -285,6 +285,9 @@ int bpf_prog_array_copy_to_user(struct bpf_prog_array __rcu *progs,#ifdef CONFIG_BPF_SYSCALL DECLARE_PER_CPU (int, bpf_prog_active); +extern const struct file_operations bpf_map_fops; +extern const struct file_operations bpf_prog_fops; +#define BPF_PROG_TYPE (_id, _ops) \ extern const struct bpf_verifier_ops _ops;#define
BPF_MAP_TYPE(_id, _ops)\include/linux/lsm_hooks.h +2
-0@@ -1385,6 +1385,19 @@* @bpf_prog_free_security: * Clean up the security information stored inside bpf prog. * +* @bpf_map_file: +* When creating a bpf map fd, set up the file security information with
+ * the bpf security information stored in the map struct. So
when the map
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
+ *
+ * @bpf_prog_file:
+ * When creating a bpf prog fd, set up the file security
information with
+ * the bpf security information stored in the prog struct. So
when the prog
+ * fd is passed between processes, the security module can
directly read
+ * the security information from file security struct rather
than the bpf
+ * security struct.
*/union security_list_options { int (*binder_set_context_mgr)(struct task_struct *mgr);include/linux/lsm_hooks.h +2
-0@@ -1726,6 +1739,8 @@ union security_list_options {void (*bpf_map_free_security)(struct bpf_map *map);int (*bpf_prog_alloc_security)(struct bpf_prog_aux *aux);void (*bpf_prog_free_security)(struct bpf_prog_aux *aux); +void (*bpf_map_file)(struct bpf_map *map,struct file *file); +void (*bpf_prog_file)(struct bpf_prog_aux *aux,struct file *file);#endif /* CONFIG_BPF_SYSCALL */ };
include/linux/lsm_hooks.h +2
-0@@ -1954,6 +1969,8 @@ struct security_hook_heads {struct list_head bpf_map_free_security;struct list_head bpf_prog_alloc_security;struct list_head bpf_prog_free_security; +struct list_head bpf_map_file; +struct list_head bpf_prog_file;#endif /* CONFIG_BPF_SYSCALL */ } __randomize_layout;include/linux/security.h +1
-0@@ -1740,6 +1740,8 @@ extern int security_bpf_map_alloc(struct bpf_map *map);extern void security_bpf_map_free (struct bpf_map *map);extern int security_bpf_prog_alloc (struct bpf_prog_aux *aux);extern void security_bpf_prog_free (struct bpf_prog_aux *aux); +extern void security_bpf_map_file(struct bpf_map *map, structfile
*file);
+extern void security_bpf_prog_file(structbpf_prog_aux*aux, struct
file *file);
#else
static inline int security_bpf(int cmd, unionbpf_attr*attr,
unsigned int size)include/linux/security.h +2
-0@@ -1772,6 +1774,13 @@ static inline int security_bpf_prog_alloc(struct bpf_prog_aux *aux) static inline void security_bpf_prog_free(struct bpf_prog_aux *aux) { } + +static inline void security_bpf_map_file(struct bpf_map *map,struct
file *file)include/linux/security.h +3
-0+{ } + +static inline void security_bpf_prog_file(struct bpf_prog_aux*aux,
include/linux/security.h +2
-0+ struct file *file) +{ }#endif /* CONFIG_SECURITY */ #endif /* CONFIG_BPF_SYSCALL */ kernel/bpf/syscall.c +1
-1@@ -313,7 +313,7 @@ static ssize_t bpf_dummy_write(struct file *filp, const char __user *buf, return -EINVAL ; } -static const struct file_operations bpf_map_fops = { +const struct file_operations bpf_map_fops = {#ifdef CONFIG_PROC_FS .show_fdinfo =
bpf_map_show_fdinfo,
#endifkernel/bpf/syscall.c +0
-0@@ -964,7 +964,7 @@ static void bpf_prog_show_fdinfo(struct
seq_file
*m, struct file *filp)
}
#endifkernel/bpf/syscall.c +1
-1-static const struct file_operations bpf_prog_fops = { +const struct file_operations bpf_prog_fops = { #ifdef CONFIG_PROC_FS .show_fdinfo = bpf_prog_show_fdinfo, #endifsecurity/security.c +1
-0@@ -1734,4 +1734,12 @@ void security_bpf_prog_free(struct bpf_prog_aux *aux) {call_void_hook (bpf_prog_free_security, aux); } +void security_bpf_map_file(struct bpf_map *map, struct file*file)
security/security.c +4
-0+{ +call_void_hook (bpf_map_file, map, file); +} +void security_bpf_prog_file(struct bpf_prog_aux *aux, structfile
*file)security/security.c +3
-0+{ +call_void_hook (bpf_prog_file, aux, file); +}#endif /* CONFIG_BPF_SYSCALL */ security/selinux/hooks.c +4
-0@@ -1815,6 +1815,10 @@ static inline int file_path_has_perm(conststruct cred *cred, return inode_has_perm(cred, file_inode(file), av, &ad); } +#ifdef CONFIG_BPF_SYSCALL +static int bpf_file_check (struct file *file,u32 sid); +#endif +/* Check whether a task can use an open file descriptor to access an inode in a given way. Check access to the descriptor itself, and then use
dentry_has_permtosecurity/selinux/hooks.c +6
-0@@ -1845,6 +1849,12 @@ static int file_has_perm(const struct cred *cred, goto out; } +#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file,cred_sid (cred)); +if (rc) + goto out; +#endif +/* av is zero if only checking access to the descriptor. */ rc =0 ;if (av)security/selinux/hooks.c +0
-0@@ -2165,6 +2175,12 @@ static intselinux_binder_transfer_file(struct
task_struct*from,return rc; }security/selinux/hooks.c +7
-0+#ifdef CONFIG_BPF_SYSCALL + rc =bpf_file_check (file, sid); +if (rc) +return rc; +#endif +if (unlikely (IS_PRIVATE (d_backing_inode (dentry))))return 0 ;@@ -6288,6 +6304,33 @@ static u32 bpf_map_fmode_to_av(fmode_t fmode)return av; } +/* This function will check the file pass through unix socket or binder to see
+ * if it is a bpf related object. And apply correspinding checks on
the bpf
+ * object based on the type. The bpf maps and programs, not like other files and
+ * socket, are using a shared anonymous inode inside the kernel as
their inode.
+ * So checking that inode cannot identify if the process have privilege to
+ * access the bpf object and that's why we have to add this additional check in
+ *selinux_file_receiveandselinux_binder_transfer_files.
+ */security/selinux/hooks.c +7
-0+static int bpf_file_check (struct file *file,u32 sid) +{ +struct file_security_struct *fsec = file->f_security; +int ret; + +if (file->f_op == &bpf_map_fops) { + ret = avc_has_perm(sid, fsec->sid,
SECCLASS_BPF_MAP,
+ bpf_map_fmode_to_av(file-Quoted 1 line
f_mode), NULL);security/selinux/hooks.c +4
-0+if (ret) +return ret; + }else if (file->f_op == &bpf_prog_fops) { + ret = avc_has_perm(sid, fsec->sid,
SECCLASS_BPF_PROG,security/selinux/hooks.c +9
-0+ BPF_PROG__USE, NULL); +if (ret) +return ret; + } +return 0 ; +} +static int selinux_bpf_map (struct bpf_map *map,fmode_t fmode) {u32 sid =current_sid ();@@ -6351,6 +6394,22 @@ static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) aux->security = NULL;kfree (bpfsec); } + +static void selinux_bpf_map_file(struct bpf_map *map, structfile
*file)security/selinux/hooks.c +8
-0+{ +struct bpf_security_struct *bpfsec = map->security; +struct file_security_struct *fsec = file->f_security; + + fsec->sid = bpfsec->sid; +} + +static void selinux_bpf_prog_file(struct bpf_prog_aux *aux,struct
file *file)security/selinux/hooks.c +2
-0+{ +struct bpf_security_struct *bpfsec = aux->security;Quoted 9 lines
security/selinux/hooks.c static void selinux_bpf_prog_free(struct bpf_prog_aux *aux) · line 6403
Quoted 3 lines
security/selinux/hooks.c +3
-0+struct file_security_struct *fsec = file->f_security; + + fsec->sid = bpfsec->sid;I could be wrong, but isn't it the case that
fsec->sidalready will equalbpfsec->sid, because they are both created by the same thread during the same system call, and they each inherit the SID of the current task?This is true when bpf object is created by the same process that obtains the fd. But there are other ways of getting a bpf object fd from the kernel such as
bpf_obj_getandbpf_get_obj_fd_by_id. These action will ask the kernel to allocate a new file for the bpf object and the file sid would be the process ask for fd while the bpfsec-
Quoted 7 lines
Quoted 2 lines
Quoted 1 line
sid
is the sid when bpf object get created. These two could be different.
Oh, in that case you shouldn't change the
fsec->sid; you'll need to use thebpfsec->sidin your checks instead. But you can still do what I described below.
Okay, I will add a bpf flag and a bpf sid in the file security struct to store the flag and sid for selinux checking when fd get transfered.
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
What I expected you to do was to add and set a flags field in the
file_security_structto indicate that this is a bpf map or prog, and
then test for that in yourbpf_file_check()function instead of having
to export and test the fops structures.Quoted 3 lines
+}
#endif
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
static struct
security_hook_listselinux_hooks[]__lsm_ro_after_init
= {security/selinux/hooks.c +0
-0@@ -6581,6 +6640,8 @@ static struct security_hook_list selinux_hooks[] __lsm_ro_after_init = { LSM_HOOK_INIT(bpf_prog_alloc_security, selinux_bpf_prog_alloc),Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
security/selinux/hooks.c +2
-0LSM_HOOK_INIT (bpf_map_free_security, selinux_bpf_map_free),LSM_HOOK_INIT (bpf_prog_free_security, selinux_bpf_prog_free), +LSM_HOOK_INIT (bpf_map_file, selinux_bpf_map_file), + LSM_HOOK_INIT(bpf_prog_file, selinux_bpf_prog_file),#endif
};
--
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