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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ e580323ac0b51ad10ec2e181d1f777479b7983e7 and < 6cd84cefd8b73e85b9eda17b319bd40a670f3a38≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < fe3b45b56b6c3d4b6b341de27fa291005287a21c≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < cb3420c047957e565101585bb4f15e1a6e3de6b0≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < 7ce4c23e783e766507b2cef27bbf97e9ca944f1a≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < 84008bf1860e0ef8059a7583a1163f36b704d08a≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < 46d59ff421824b6483549d87f14efffbbbd1f6cb≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and < 70a38f87bed7f0694fd07988b47b2db1e10d8df3 and 2 more≥ 5.10.220 and < 5.10.261version 5.15 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/70a38f87bed7f0694fd07988b47b2db1e10d8df3
- git.kernel.org/stable/c/84008bf1860e0ef8059a7583a1163f36b704d08a
- git.kernel.org/stable/c/cb3420c047957e565101585bb4f15e1a6e3de6b0
- git.kernel.org/stable/c/3a5c55a19cad62f2973be25fe96a1a9e7f618e8a
- git.kernel.org/stable/c/6cd84cefd8b73e85b9eda17b319bd40a670f3a38
- git.kernel.org/stable/c/fe3b45b56b6c3d4b6b341de27fa291005287a21c
- git.kernel.org/stable/c/46d59ff421824b6483549d87f14efffbbbd1f6cb
- git.kernel.org/stable/c/7ce4c23e783e766507b2cef27bbf97e9ca944f1a
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72218 is "lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.