Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89485lockd: pin next file across nlm_inspect_file lock-drop

Description

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. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89485, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.71% · top 46% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < e3c413f789eaf0170275c7eba523ead73d963f30
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < 08a455f87b14c7ff22ae3fdadda62a796a3a5572
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < 550c19222c7132c888e23c9d89079ba1c9bc4cca
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < 350087f231c11efcd288c310707c40eab63ca583
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < c24bdb7df2f34bdc38ca8a73796f5acb40f1830c
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < 41f0a6d31615fcae261bf28a0aa50050dc93a401
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < e999a88133654c6dfc68487fb49da5f20dfa2d4f
    • affected 01df9c5e918ae5559f2d96da0143f8bfbb9e6171 – < 526c49cff3f72c3ec74752016380c7567040581b
  • Linux · Linux

    • affected 2.6.18
    • unaffected < 2.6.18
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89485 badge
[![CVE-2026-89485](https://cveledger.app/badge/CVE-2026-89485.svg)](https://cveledger.app/cve/CVE-2026-89485)

Record last updated .