Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-89485

lockd: pin next file across nlm_inspect_file lock-drop

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlm_inspect_file lock-drop nlm_traverse_files() pins the current file with f_count++ across a mutex_unlock for nlm_inspect_file(), but nothing pins the saved next pointer. A concurrent nlm_release_file() can kfree the next file during the unlock window, and the iterator dereferences freed memory on the next loop step. Pin both current and next before the lock-drop. Advance by swapping the pinned cursors at the end of each iteration so next is always held alive across the unlock. Always call nlm_file_release() after dropping the iteration pin, regardless of whether the file matched the predicate. Use nlm_file_inuse(), which does a live walk of the inode lock list, rather than the cached f_locks field, so skipped files that never ran nlm_inspect_file() are evaluated correctly. Because every file in a hash bucket is now pinned and released, files skipped by the is_failover_file predicate that have no locks, blocks, shares, or external references are deleted during traversal. The old code never evaluated skipped files for cleanup. The new behavior is intentional: such files are stale and should not persist in the table.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in e3c413f789eaf0170275c7eba523ead73d963f30; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in 08a455f87b14c7ff22ae3fdadda62a796a3a5572; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in 550c19222c7132c888e23c9d89079ba1c9bc4cca; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in 350087f231c11efcd288c310707c40eab63ca583; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in c24bdb7df2f34bdc38ca8a73796f5acb40f1830c; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in 41f0a6d31615fcae261bf28a0aa50050dc93a401; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in e999a88133654c6dfc68487fb49da5f20dfa2d4f; From 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 · fixed in 526c49cff3f72c3ec74752016380c7567040581b

  • Linux Linux

    2.6.18

  • KernelLinux

    From 2.6.18 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4

References 8

git.kernel.org