diff options
author | Christian Brauner <[email protected]> | 2021-01-21 14:19:42 +0100 |
---|---|---|
committer | Christian Brauner <[email protected]> | 2021-01-24 14:27:19 +0100 |
commit | 1ab29965b30599c797266eb3b970b4e6c8de3672 (patch) | |
tree | 3fcc302263b0b5a129712eef9716e1cf9ef9e2ff /security/integrity/ima/ima_api.c | |
parent | 435ac6214e00eab191296cd6cfdc316aa07e7794 (diff) |
exec: handle idmapped mounts
When executing a setuid binary the kernel will verify in bprm_fill_uid()
that the inode has a mapping in the caller's user namespace before
setting the callers uid and gid. Let bprm_fill_uid() handle idmapped
mounts. If the inode is accessed through an idmapped mount it is mapped
according to the mount's user namespace. Afterwards the checks are
identical to non-idmapped mounts. If the initial user namespace is
passed nothing changes so non-idmapped mounts will see identical
behavior as before.
Link: https://lore.kernel.org/r/[email protected]
Cc: Christoph Hellwig <[email protected]>
Cc: David Howells <[email protected]>
Cc: Al Viro <[email protected]>
Cc: [email protected]
Reviewed-by: Christoph Hellwig <[email protected]>
Reviewed-by: James Morris <[email protected]>
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'security/integrity/ima/ima_api.c')
0 files changed, 0 insertions, 0 deletions