Answer in brief
CVE-2026-89485 records a Unknown severity vulnerability in lockd: pin next file across nlm_inspect_file lock-drop. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <c24bdb7df2f34bdc38ca8a73796f5acb40f1830c || >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <41f0a6d31615fcae261bf28a0aa50050dc93a401 || >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <e999a88133654c6dfc68487fb49da5f20dfa2d4f || >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <526c49cff3f72c3ec74752016380c7567040581b | c24bdb7df2f34bdc38ca8a73796f5acb40f1830c, 41f0a6d31615fcae261bf28a0aa50050dc93a401, e999a88133654c6dfc68487fb49da5f20dfa2d4f, 526c49cff3f72c3ec74752016380c7567040581b |
| Linux/Linuxgeneric | 2.6.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.