NFS: Fix access to suid/sgid executables

nfs_open_permission_mask() shouldn't check MAY_READ for suid/sgid files that are opened with __FMODE_EXEC.

Also fix NFSv4 access-in-open path in a similar way -- openflags must be used because fmode will not always have FMODE_EXEC set.

Signed-off-by Weston Andros Adamson <[email protected]>

---

This patch fixes https://bugzilla.kernel.org/show_bug.cgi?id=49101

The fix is not as obvious or clean as I'd like, so here is a little background:

Not checking MAY_READ when a S_ISUID or S_ISGID file has MAY_EXEC causes suid/sgid executables to behave the same as on a local FS.

The second part is fixing open-in-access for NFSv4 - we want to do the same thing as in nfs_open_permission_mask, but oddly enough fmode doesn't always indicate that the file is being opened for execution. Instead we have to use the openflags for this.

Adding some debug prints show that the first exec of a suid/sgid file will open with fmode containing FMODE_EXEC and FMODE_READ, but subsequent execs will open with fmode containing FMODE_READ, but not FMODE_EXEC. openflags always has __FMODE_EXEC set in these examples.

The first exec has these values in nfs4_opendata_access():

fmode = 0x21: contains read exec
openflags = 0x8020: contains exec

The second (and subsequent) execs have these values in nfs4_opendata_access():

fmode = 0x1: contains read
openflags = 0x8020: contains exec

-dros

 fs/nfs/dir.c      |   12 +-+-+-+-+-+-+-+-+----
 fs/nfs/nfs4proc.c |   13 +-+-+-+-+-+-+-+-+-+-+---
 2 files changed, 20 insertions(+-), 5 deletions(-)

fs/nfs/dir.c +1 -1

index 32e6c53..5141243 100644
--- a/fs/nfs/dir.c
+-+-+- b/fs/nfs/dir.c

@@ -2149,7 +-2149,7 @@ out:

fs/nfs/dir.c +1 -1

 	return -EACCES;
 }
 
-static int nfs_open_permission_mask(int openflags)
+-static int nfs_open_permission_mask(struct inode *inode, int openflags)
 {
 	int mask = 0;

@@ -2157,14 +-2157,20 @@ static int nfs_open_permission_mask(int openflags)

+-	}
+-

fs/nfs/dir.c +2 -1

 	return mask;
 }
 
 int nfs_may_open(struct inode *inode, struct rpc_cred *cred, int openflags)
 {
-	return nfs_do_access(inode, cred, nfs_open_permission_mask(openflags));
+-	return nfs_do_access(inode, cred,
+-		nfs_open_permission_mask(inode, openflags));
 }
 EXPORT_SYMBOL_GPL(nfs_may_open);

fs/nfs/nfs4proc.c +1 -1

index 5d864fb..23cf1a8 100644
--- a/fs/nfs/nfs4proc.c
+-+-+- b/fs/nfs/nfs4proc.c

@@ -1626,7 +-1626,8 @@ static int _nfs4_recover_proc_open(struct nfs4_opendata *data)

static int nfs4_opendata_access(struct rpc_cred *cred,

fs/nfs/nfs4proc.c +2 -1

 				struct nfs4_opendata *opendata,
-				struct nfs4_state *state, fmode_t fmode)
+-				struct nfs4_state *state, fmode_t fmode,
+-				int openflags)
 {
 	struct nfs_access_entry cache;
 	u32 mask;

@@ -1644,6 +-1645,14 @@ static int nfs4_opendata_access(struct rpc_cred *cred,

+-

fs/nfs/nfs4proc.c +0 -0

 	cache.cred = cred;
 	cache.jiffies = jiffies;
 	nfs_access_set_mask(&cache, opendata->o_res.access_result);

@@ -1896,7 +-1905,7 @@ static int _nfs4_do_open(struct inode *dir,

fs/nfs/nfs4proc.c +1 -1

 	if (server->caps & NFS_CAP_POSIX_LOCK)
 		set_bit(NFS_STATE_POSIX_LOCKS, &state->flags);
 
-	status = nfs4_opendata_access(cred, opendata, state, fmode);
+-	status = nfs4_opendata_access(cred, opendata, state, fmode, flags);
 	if (status != 0)
 		goto err_opendata_put;

Quoted 55 lines · Weston Andros Adamson

nfs_open_permission_mask() shouldn't check MAY_READ for suid/sgid files that are opened with __FMODE_EXEC.

Also fix NFSv4 access-in-open path in a similar way -- openflags must be used because fmode will not always have FMODE_EXEC set.

Signed-off-by Weston Andros Adamson <[email protected]>

---

This patch fixes https://bugzilla.kernel.org/show_bug.cgi?id=49101

The fix is not as obvious or clean as I'd like, so here is a little background:

Not checking MAY_READ when a S_ISUID or S_ISGID file has MAY_EXEC causes suid/sgid executables to behave the same as on a local FS.

The second part is fixing open-in-access for NFSv4 - we want to do the same thing as in nfs_open_permission_mask, but oddly enough fmode doesn't always indicate that the file is being opened for execution. Instead we have to use the openflags for this.

Adding some debug prints show that the first exec of a suid/sgid file will open with fmode containing FMODE_EXEC and FMODE_READ, but subsequent execs will open with fmode containing FMODE_READ, but not FMODE_EXEC. openflags always has __FMODE_EXEC set in these examples.

The first exec has these values in nfs4_opendata_access():

fmode = 0x21: contains read exec
openflags = 0x8020: contains exec

The second (and subsequent) execs have these values in nfs4_opendata_access():

fmode = 0x1: contains read
openflags = 0x8020: contains exec

-dros

fs/nfs/dir.c      |   12 +++++++++---
fs/nfs/nfs4proc.c |   13 +++++++++++--
2 files changed, 20 insertions(+), 5 deletions(-)

fs/nfs/dir.c +1 -1

index 32e6c53..5141243 100644
@@ -2149,7 +2149,7 @@ out:
 	return -EACCES;
 }
 
-static int nfs_open_permission_mask(int openflags)
+static int nfs_open_permission_mask(struct inode *inode, int openflags)
 {
 	int mask = 0;
 

fs/nfs/dir.c static int nfs_open_permission_mask(int openflags) · line 2164

Quoted 10 lines

fs/nfs/dir.c +4 -1

@@ -2157,14 +2157,20 @@ static int nfs_open_permission_mask(int openflags)
 		mask |= MAY_READ;
 	if ((openflags & O_ACCMODE) != O_RDONLY)
 		mask |= MAY_WRITE;
-	if (openflags & __FMODE_EXEC)
+	if (openflags & __FMODE_EXEC) {
 		mask |= MAY_EXEC;
+		/* don't check MAY_READ for exec of suid/sgid */
+		if (inode->i_mode & (S_ISUID | S_ISGID))
+			mask &= ~MAY_READ;

Wait, this can't be right. Why does the presence of a suid/sgid flag make a difference here? Either way, if __FMODE_EXEC access is requested, then we should only need MAY_EXEC rights.

Quoted 29 lines

fs/nfs/dir.c +4 -1

+	}
+
 	return mask;
 }
 
 int nfs_may_open(struct inode *inode, struct rpc_cred *cred, int openflags)
 {
-	return nfs_do_access(inode, cred, nfs_open_permission_mask(openflags));
+	return nfs_do_access(inode, cred,
+		nfs_open_permission_mask(inode, openflags));
 }
 EXPORT_SYMBOL_GPL(nfs_may_open);
 

fs/nfs/nfs4proc.c +2 -1

index 5d864fb..23cf1a8 100644
@@ -1626,7 +1626,8 @@ static int _nfs4_recover_proc_open(struct nfs4_opendata *data)
 
 static int nfs4_opendata_access(struct rpc_cred *cred,
 				struct nfs4_opendata *opendata,
-				struct nfs4_state *state, fmode_t fmode)
+				struct nfs4_state *state, fmode_t fmode,
+				int openflags)
 {
 	struct nfs_access_entry cache;
 	u32 mask;

fs/nfs/nfs4proc.c static int nfs4_opendata_access(struct rpc_cred *cred, · line 1654

Quoted 10 lines

fs/nfs/nfs4proc.c +7 -0

@@ -1644,6 +1645,14 @@ static int nfs4_opendata_access(struct rpc_cred *cred,
 	if (fmode & FMODE_EXEC)
 		mask |= MAY_EXEC;
 
+	/* use openflags to check for exec of suid/sgid, because fmode won't
+	 * always have FMODE_EXEC set by VFS.
+	 * Also, don't check MAY_READ on a suid/sgid file being executed */
+	if ((openflags & __FMODE_EXEC) &&
+	    (state->inode->i_mode & (S_ISUID | S_ISGID))) {
+		mask = MAY_EXEC;
+	}

Ditto...

Quoted 13 lines

fs/nfs/nfs4proc.c +2 -1

+
 	cache.cred = cred;
 	cache.jiffies = jiffies;
 	nfs_access_set_mask(&cache, opendata->o_res.access_result);

@@ -1896,7 +1905,7 @@ static int _nfs4_do_open(struct inode *dir,
 	if (server->caps & NFS_CAP_POSIX_LOCK)
 		set_bit(NFS_STATE_POSIX_LOCKS, &state->flags);
 
-	status = nfs4_opendata_access(cred, opendata, state, fmode);
+	status = nfs4_opendata_access(cred, opendata, state, fmode, flags);
 	if (status != 0)
 		goto err_opendata_put;
 

Signature · 6 lines

Trond Myklebust
Linux NFS client maintainer

NetApp
[email protected]
www.netapp.com