Skip to content

Commit

Permalink
vfs: open() with O_CREAT should not create inodes with unknown ids
Browse files Browse the repository at this point in the history
may_create() rejects creation of inodes with ids which lack a
mapping into s_user_ns. However for O_CREAT may_o_create() is
is used instead. Add a similar check there.

Fixes: 036d523 ("vfs: Don't create inodes with a uid or gid unknown to the vfs")
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
  • Loading branch information
Seth Forshee authored and ebiederm committed Feb 1, 2017
1 parent 68eb94f commit 1328c72
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions fs/namei.c
Original file line number Diff line number Diff line change
Expand Up @@ -2941,10 +2941,16 @@ static inline int open_to_namei_flags(int flag)

static int may_o_create(const struct path *dir, struct dentry *dentry, umode_t mode)
{
struct user_namespace *s_user_ns;
int error = security_path_mknod(dir, dentry, mode, 0);
if (error)
return error;

s_user_ns = dir->dentry->d_sb->s_user_ns;
if (!kuid_has_mapping(s_user_ns, current_fsuid()) ||
!kgid_has_mapping(s_user_ns, current_fsgid()))
return -EOVERFLOW;

error = inode_permission(dir->dentry->d_inode, MAY_WRITE | MAY_EXEC);
if (error)
return error;
Expand Down

0 comments on commit 1328c72

Please sign in to comment.