https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:05:31 +0000 https://vulnerability.circl.lu/vuln/cve-2026-72472 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfs: use nfsi-&gt;rwsem to protect traversal of the file lock list</p> <p>Lingfeng identified a bug and suggested two solutions, but both appear to have issues.</p> <p>Generally, we cannot release flc_lock while iterating over the file lock list to avoid use-after-free (UAF) problems with file locks. However, functions like nfs_delegation_claim_locks and nfs4_reclaim_locks cannot adhere to this rule because recover_lock or nfs4_lock_delegation_recall may take a long time. To resolve this, NFS switches to using nfsi-&gt;rwsem for the same protection, and nfs_reclaim_locks follows this approach. Although nfs_delegation_claim_locks uses so_delegreturn_mutex instead, this is inadequate since a single inode can have multiple nfs4_state instances. Therefore, the fix is to also use nfsi-&gt;rwsem in this case.</p> <p>Furthermore, after commit c69899a17ca4 (&#34;NFSv4: Update of VFS byte range lock must be atomic with the stateid update&#34;), the functions nfs4_locku_done and nfs4_lock_done also break this rule because they call locks_lock_inode_wait without holding nfsi-&gt;rwsem. Simply adding this protection could cause many deadlocks, so instead, the call to locks_lock_inode_wait is moved into _nfs4_proc_setlk. Regarding the bug fixed by commit c69899a17ca4 (&#34;NFSv4: Update of VFS byte range lock must be atomic with the stateid update&#34;), it has been resolved after commit 0460253913e5 (&#34;NFSv4: nfs4_do_open() is incorrectly triggering state recovery&#34;…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfs: use nfsi-&gt;rwsem to protect traversal of the file lock list</p> <p>Lingfeng identified a bug and suggested two solutions, but both appear to have issues.</p> <p>Generally, we cannot release flc_lock while iterating over the file lock list to avoid use-after-free (UAF) problems with file locks. However, functions like nfs_delegation_claim_locks and nfs4_reclaim_locks cannot adhere to this rule because recover_lock or nfs4_lock_delegation_recall may take a long time. To resolve this, NFS switches to using nfsi-&gt;rwsem for the same protection, and nfs_reclaim_locks follows this approach. Although nfs_delegation_claim_locks uses so_delegreturn_mutex instead, this is inadequate since a single inode can have multiple nfs4_state instances. Therefore, the fix is to also use nfsi-&gt;rwsem in this case.</p> <p>Furthermore, after commit c69899a17ca4 (&#34;NFSv4: Update of VFS byte range lock must be atomic with the stateid update&#34;), the functions nfs4_locku_done and nfs4_lock_done also break this rule because they call locks_lock_inode_wait without holding nfsi-&gt;rwsem. Simply adding this protection could cause many deadlocks, so instead, the call to locks_lock_inode_wait is moved into _nfs4_proc_setlk. Regarding the bug fixed by commit c69899a17ca4 (&#34;NFSv4: Update of VFS byte range lock must be atomic with the stateid update&#34;), it has been resolved after commit 0460253913e5 (&#34;NFSv4: nfs4_do_open() is incorrectly triggering state recovery&#34;…</p> https://vulnerability.circl.lu/vuln/cve-2026-72472