Re: [PATCH v2] nfs: fix the race of lock/unlock and open

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Friendly ping..

Thanks

在 2025/7/15 11:05, Li Lingfeng 写道:
LOCK may extend an existing lock and release another one and UNLOCK may
also release an existing lock.
When opening a file, there may be access to file locks that have been
concurrently released by lock/unlock operations, potentially triggering
UAF.
While certain concurrent scenarios involving lock/unlock and open
operations have been safeguarded with locks – for example,
nfs4_proc_unlckz() acquires the so_delegreturn_mutex prior to invoking
locks_lock_inode_wait() – there remain cases where such protection is not
yet implemented.

The issue can be reproduced through the following steps:
T1: open in read-only mode with three consecutive lock operations applied
     lock1(0~100) --> add lock1 to file
     lock2(120~200) --> add lock2 to file
     lock3(50~150) --> extend lock1 to cover range 0~200 and release lock2
T2: restart nfs-server and run state manager
T3: open in write-only mode
     T1                            T2                                T3
                             start recover
lock1
lock2
                             nfs4_open_reclaim
                             clear_bit // NFS_DELEGATED_STATE
lock3
  _nfs4_proc_setlk
   lock so_delegreturn_mutex
   unlock so_delegreturn_mutex
   _nfs4_do_setlk
                             recover done
                                                 lock so_delegreturn_mutex
                                                 nfs_delegation_claim_locks
                                                 get lock2
    rpc_run_task
    ...
    nfs4_lock_done
     locks_lock_inode_wait
     ...
      locks_dispose_list
      free lock2
                                                 use lock2
                                                 // UAF
                                                 unlock so_delegreturn_mutex

Protect file lock by nfsi->rwsem to fix this issue.

Fixes: c69899a17ca4 ("NFSv4: Update of VFS byte range lock must be atomic with the stateid update")
Reported-by: zhangjian (CG) <zhangjian496@xxxxxxxxxx>
Suggested-by: yangerkun <yangerkun@xxxxxxxxxx>
Signed-off-by: Li Lingfeng <lilingfeng3@xxxxxxxxxx>
---
Changes in v2:
   Use nfsi->rwsem instead of sp->so_delegreturn_mutex to prevent concurrency.

  fs/nfs/delegation.c | 5 ++++-
  fs/nfs/nfs4proc.c   | 8 +++++++-
  2 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/delegation.c b/fs/nfs/delegation.c
index 10ef46e29b25..4467b4f61905 100644
--- a/fs/nfs/delegation.c
+++ b/fs/nfs/delegation.c
@@ -149,15 +149,17 @@ int nfs4_check_delegation(struct inode *inode, fmode_t type)
  static int nfs_delegation_claim_locks(struct nfs4_state *state, const nfs4_stateid *stateid)
  {
  	struct inode *inode = state->inode;
+	struct nfs_inode *nfsi = NFS_I(inode);
  	struct file_lock *fl;
  	struct file_lock_context *flctx = locks_inode_context(inode);
  	struct list_head *list;
  	int status = 0;
if (flctx == NULL)
-		goto out;
+		return status;
list = &flctx->flc_posix;
+	down_write(&nfsi->rwsem);
  	spin_lock(&flctx->flc_lock);
  restart:
  	for_each_file_lock(fl, list) {
@@ -175,6 +177,7 @@ static int nfs_delegation_claim_locks(struct nfs4_state *state, const nfs4_state
  	}
  	spin_unlock(&flctx->flc_lock);
  out:
+	up_write(&nfsi->rwsem);
  	return status;
  }
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 341740fa293d..06f109c7eb2e 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -7294,14 +7294,18 @@ static int nfs4_proc_unlck(struct nfs4_state *state, int cmd, struct file_lock *
  	status = -ENOMEM;
  	if (IS_ERR(seqid))
  		goto out;
+	down_read(&nfsi->rwsem);
  	task = nfs4_do_unlck(request,
  			     nfs_file_open_context(request->c.flc_file),
  			     lsp, seqid);
  	status = PTR_ERR(task);
-	if (IS_ERR(task))
+	if (IS_ERR(task)) {
+		up_read(&nfsi->rwsem);
  		goto out;
+	}
  	status = rpc_wait_for_completion_task(task);
  	rpc_put_task(task);
+	up_read(&nfsi->rwsem);
  out:
  	request->c.flc_flags = saved_flags;
  	trace_nfs4_unlock(request, state, F_SETLK, status);
@@ -7642,7 +7646,9 @@ static int _nfs4_proc_setlk(struct nfs4_state *state, int cmd, struct file_lock
  	}
  	up_read(&nfsi->rwsem);
  	mutex_unlock(&sp->so_delegreturn_mutex);
+	down_read(&nfsi->rwsem);
  	status = _nfs4_do_setlk(state, cmd, request, NFS_LOCK_NEW);
+	up_read(&nfsi->rwsem);
  out:
  	request->c.flc_flags = flags;
  	return status;




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux