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-72218lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure

Description

In the Linux kernel, the following vulnerability has been resolved: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure The cached-file path in nlm_lookup_file() reaches the found: label unconditionally, even when nlm_do_fopen() fails. At that label *result and file->f_count are updated before the error is returned. The wrappers nlm3svc_lookup_file() and nlm4svc_lookup_file() then bail out of their switch without copying *result back to their caller, so the proc handler's local nlm_file pointer remains NULL and the cleanup path skips nlm_release_file(). The f_count increment is never released, and nlm_traverse_files() can no longer reap the file because its refcount never returns to zero between requests. Short-circuit the cached path so neither *result nor f_count is touched when nlm_do_fopen() fails on a hashed nlm_file.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e580323ac0b51ad10ec2e181d1f777479b7983e7 – < 6cd84cefd8b73e85b9eda17b319bd40a670f3a38
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < fe3b45b56b6c3d4b6b341de27fa291005287a21c
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < cb3420c047957e565101585bb4f15e1a6e3de6b0
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 7ce4c23e783e766507b2cef27bbf97e9ca944f1a
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 84008bf1860e0ef8059a7583a1163f36b704d08a
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 46d59ff421824b6483549d87f14efffbbbd1f6cb
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 70a38f87bed7f0694fd07988b47b2db1e10d8df3
    • affected 5.10.220 – < 5.10.261
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .