![]() New inodes are created in a two stage process. We first will compute the label on a new inode in security_inode_create() and check if the operation is allowed. We will then actually re-compute that same label and apply it in security_inode_init_security(). The change to do new label calculations based in part on the last component of the path name only passed the path component information all the way down the security_inode_init_security hook. Down the security_inode_create hook the path information did not make it past may_create. Thus the two calculations came up differently and the permissions check might not actually be against the label that is created. Pass and use the same information in both places to harmonize the calculations and checks. Reported-by: Dominick Grift <domg472@gmail.com> Signed-off-by: Eric Paris <eparis@redhat.com> |
||
---|---|---|
.. | ||
apparmor | ||
integrity/ima | ||
keys | ||
selinux | ||
smack | ||
tomoyo | ||
capability.c | ||
commoncap.c | ||
device_cgroup.c | ||
inode.c | ||
Kconfig | ||
lsm_audit.c | ||
Makefile | ||
min_addr.c | ||
security.c |