{"api_version":"1","generated_at":"2026-09-12T11:59:02+00:00","cve":"CVE-2026-89485","urls":{"html":"https://cve.report/CVE-2026-89485","api":"https://cve.report/api/cve/CVE-2026-89485.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89485","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89485"},"summary":{"title":"lockd: pin next file across nlm_inspect_file lock-drop","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: pin next file across nlm_inspect_file lock-drop\n\nnlm_traverse_files() pins the current file with f_count++ across\na mutex_unlock for nlm_inspect_file(), but nothing pins the saved\nnext pointer.  A concurrent nlm_release_file() can kfree the next\nfile during the unlock window, and the iterator dereferences freed\nmemory on the next loop step.\n\nPin both current and next before the lock-drop.  Advance by\nswapping the pinned cursors at the end of each iteration so next\nis always held alive across the unlock.\n\nAlways call nlm_file_release() after dropping the iteration pin,\nregardless of whether the file matched the predicate.  Use\nnlm_file_inuse(), which does a live walk of the inode lock list,\nrather than the cached f_locks field, so skipped files that never\nran nlm_inspect_file() are evaluated correctly.\n\nBecause every file in a hash bucket is now pinned and released,\nfiles skipped by the is_failover_file predicate that have no\nlocks, blocks, shares, or external references are deleted during\ntraversal.  The old code never evaluated skipped files for\ncleanup.  The new behavior is intentional: such files are stale\nand should not persist in the table.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:30","updated_at":"2026-09-11 20:19:30"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/526c49cff3f72c3ec74752016380c7567040581b","name":"https://git.kernel.org/stable/c/526c49cff3f72c3ec74752016380c7567040581b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e999a88133654c6dfc68487fb49da5f20dfa2d4f","name":"https://git.kernel.org/stable/c/e999a88133654c6dfc68487fb49da5f20dfa2d4f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c24bdb7df2f34bdc38ca8a73796f5acb40f1830c","name":"https://git.kernel.org/stable/c/c24bdb7df2f34bdc38ca8a73796f5acb40f1830c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/41f0a6d31615fcae261bf28a0aa50050dc93a401","name":"https://git.kernel.org/stable/c/41f0a6d31615fcae261bf28a0aa50050dc93a401","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89485","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89485","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 c24bdb7df2f34bdc38ca8a73796f5acb40f1830c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 41f0a6d31615fcae261bf28a0aa50050dc93a401 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 e999a88133654c6dfc68487fb49da5f20dfa2d4f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 526c49cff3f72c3ec74752016380c7567040581b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/lockd/svcsubs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c24bdb7df2f34bdc38ca8a73796f5acb40f1830c","status":"affected","version":"01df9c5e918ae5559f2d96da0143f8bfbb9e6171","versionType":"git"},{"lessThan":"41f0a6d31615fcae261bf28a0aa50050dc93a401","status":"affected","version":"01df9c5e918ae5559f2d96da0143f8bfbb9e6171","versionType":"git"},{"lessThan":"e999a88133654c6dfc68487fb49da5f20dfa2d4f","status":"affected","version":"01df9c5e918ae5559f2d96da0143f8bfbb9e6171","versionType":"git"},{"lessThan":"526c49cff3f72c3ec74752016380c7567040581b","status":"affected","version":"01df9c5e918ae5559f2d96da0143f8bfbb9e6171","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/lockd/svcsubs.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.18"},{"lessThan":"2.6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"2.6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"2.6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"2.6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"2.6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: pin next file across nlm_inspect_file lock-drop\n\nnlm_traverse_files() pins the current file with f_count++ across\na mutex_unlock for nlm_inspect_file(), but nothing pins the saved\nnext pointer.  A concurrent nlm_release_file() can kfree the next\nfile during the unlock window, and the iterator dereferences freed\nmemory on the next loop step.\n\nPin both current and next before the lock-drop.  Advance by\nswapping the pinned cursors at the end of each iteration so next\nis always held alive across the unlock.\n\nAlways call nlm_file_release() after dropping the iteration pin,\nregardless of whether the file matched the predicate.  Use\nnlm_file_inuse(), which does a live walk of the inode lock list,\nrather than the cached f_locks field, so skipped files that never\nran nlm_inspect_file() are evaluated correctly.\n\nBecause every file in a hash bucket is now pinned and released,\nfiles skipped by the is_failover_file predicate that have no\nlocks, blocks, shares, or external references are deleted during\ntraversal.  The old code never evaluated skipped files for\ncleanup.  The new behavior is intentional: such files are stale\nand should not persist in the table."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:43:39.403Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c24bdb7df2f34bdc38ca8a73796f5acb40f1830c"},{"url":"https://git.kernel.org/stable/c/41f0a6d31615fcae261bf28a0aa50050dc93a401"},{"url":"https://git.kernel.org/stable/c/e999a88133654c6dfc68487fb49da5f20dfa2d4f"},{"url":"https://git.kernel.org/stable/c/526c49cff3f72c3ec74752016380c7567040581b"}],"title":"lockd: pin next file across nlm_inspect_file lock-drop","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89485","datePublished":"2026-09-11T19:43:39.403Z","dateReserved":"2026-09-11T19:38:34.712Z","dateUpdated":"2026-09-11T19:43:39.403Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:30","lastModifiedDate":"2026-09-11 20:19:30","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89485","Ordinal":"1","Title":"lockd: pin next file across nlm_inspect_file lock-drop","CVE":"CVE-2026-89485","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89485","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: pin next file across nlm_inspect_file lock-drop\n\nnlm_traverse_files() pins the current file with f_count++ across\na mutex_unlock for nlm_inspect_file(), but nothing pins the saved\nnext pointer.  A concurrent nlm_release_file() can kfree the next\nfile during the unlock window, and the iterator dereferences freed\nmemory on the next loop step.\n\nPin both current and next before the lock-drop.  Advance by\nswapping the pinned cursors at the end of each iteration so next\nis always held alive across the unlock.\n\nAlways call nlm_file_release() after dropping the iteration pin,\nregardless of whether the file matched the predicate.  Use\nnlm_file_inuse(), which does a live walk of the inode lock list,\nrather than the cached f_locks field, so skipped files that never\nran nlm_inspect_file() are evaluated correctly.\n\nBecause every file in a hash bucket is now pinned and released,\nfiles skipped by the is_failover_file predicate that have no\nlocks, blocks, shares, or external references are deleted during\ntraversal.  The old code never evaluated skipped files for\ncleanup.  The new behavior is intentional: such files are stale\nand should not persist in the table.","Type":"Description","Title":"lockd: pin next file across nlm_inspect_file lock-drop"}]}}}