CVE-2026-72218
lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ e580323ac0b51ad10ec2e181d1f777479b7983e7; < 6cd84cefd8b73e85b9eda17b319bd40a670f3a38 (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < fe3b45b56b6c3d4b6b341de27fa291005287a21c (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < cb3420c047957e565101585bb4f15e1a6e3de6b0 (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 7ce4c23e783e766507b2cef27bbf97e9ca944f1a (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 84008bf1860e0ef8059a7583a1163f36b704d08a (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 46d59ff421824b6483549d87f14efffbbbd1f6cb (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a (affected, git) ≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 70a38f87bed7f0694fd07988b47b2db1e10d8df3 (affected, git) ≥ 5.10.220; < 5.10.261 (affected, semver) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.15 (affected) ≥ 0; < 5.15 (unaffected, semver) ≥ 5.10.261; ≤ 5.10.* (unaffected, semver) ≥ 5.15.212; ≤ 5.15.* (unaffected, semver) ≥ 6.1.178; ≤ 6.1.* (unaffected, semver) ≥ 6.6.145; ≤ 6.6.* (unaffected, semver) ≥ 6.12.97; ≤ 6.12.* (unaffected, semver) ≥ 6.18.40; ≤ 6.18.* (unaffected, semver) ≥ 7.1.5; ≤ 7.1.* (unaffected, semver) ≥ 7.2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/6cd84cefd8b73e85b9eda17b319bd40a670f3a38CNA: Linux
- https://git.kernel.org/stable/c/fe3b45b56b6c3d4b6b341de27fa291005287a21cCNA: Linux
- https://git.kernel.org/stable/c/cb3420c047957e565101585bb4f15e1a6e3de6b0CNA: Linux
- https://git.kernel.org/stable/c/7ce4c23e783e766507b2cef27bbf97e9ca944f1aCNA: Linux
- https://git.kernel.org/stable/c/84008bf1860e0ef8059a7583a1163f36b704d08aCNA: Linux
- https://git.kernel.org/stable/c/46d59ff421824b6483549d87f14efffbbbd1f6cbCNA: Linux
- https://git.kernel.org/stable/c/3a5c55a19cad62f2973be25fe96a1a9e7f618e8aCNA: Linux
- https://git.kernel.org/stable/c/70a38f87bed7f0694fd07988b47b2db1e10d8df3CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.