Answer in brief
CVE-2026-72218 records a Unknown severity vulnerability in lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure. 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.
Answer in brief
CVE-2026-72218 records a Unknown severity vulnerability in lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure. 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 | >=e580323ac0b51ad10ec2e181d1f777479b7983e7 <6cd84cefd8b73e85b9eda17b319bd40a670f3a38 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <fe3b45b56b6c3d4b6b341de27fa291005287a21c || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <cb3420c047957e565101585bb4f15e1a6e3de6b0 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <7ce4c23e783e766507b2cef27bbf97e9ca944f1a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <84008bf1860e0ef8059a7583a1163f36b704d08a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <46d59ff421824b6483549d87f14efffbbbd1f6cb || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <3a5c55a19cad62f2973be25fe96a1a9e7f618e8a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <70a38f87bed7f0694fd07988b47b2db1e10d8df3 || >=5.10.220 <5.10.261 | 6cd84cefd8b73e85b9eda17b319bd40a670f3a38, fe3b45b56b6c3d4b6b341de27fa291005287a21c, cb3420c047957e565101585bb4f15e1a6e3de6b0, 7ce4c23e783e766507b2cef27bbf97e9ca944f1a, 84008bf1860e0ef8059a7583a1163f36b704d08a, 46d59ff421824b6483549d87f14efffbbbd1f6cb, 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a, 70a38f87bed7f0694fd07988b47b2db1e10d8df3, 5.10.261 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
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 | >=e580323ac0b51ad10ec2e181d1f777479b7983e7 <6cd84cefd8b73e85b9eda17b319bd40a670f3a38 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <fe3b45b56b6c3d4b6b341de27fa291005287a21c || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <cb3420c047957e565101585bb4f15e1a6e3de6b0 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <7ce4c23e783e766507b2cef27bbf97e9ca944f1a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <84008bf1860e0ef8059a7583a1163f36b704d08a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <46d59ff421824b6483549d87f14efffbbbd1f6cb || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <3a5c55a19cad62f2973be25fe96a1a9e7f618e8a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <70a38f87bed7f0694fd07988b47b2db1e10d8df3 || >=5.10.220 <5.10.261 | 6cd84cefd8b73e85b9eda17b319bd40a670f3a38, fe3b45b56b6c3d4b6b341de27fa291005287a21c, cb3420c047957e565101585bb4f15e1a6e3de6b0, 7ce4c23e783e766507b2cef27bbf97e9ca944f1a, 84008bf1860e0ef8059a7583a1163f36b704d08a, 46d59ff421824b6483549d87f14efffbbbd1f6cb, 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a, 70a38f87bed7f0694fd07988b47b2db1e10d8df3, 5.10.261 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.