CVE-2026-72218

lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure

N/A
Published: August 15, 2026 at 05:54 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.220 ≤ v < 5.10.2615.15 ≤ v < 5.15.2125.15 ≤ v < 6.1.1785.15 ≤ v < 6.12.975.15 ≤ v < 6.18.405.15 ≤ v < 6.6.1455.15 ≤ v < 7.1.55.15 ≤ v < 7.25.10.2205.157f024fcd5c97dc70bb9121c80407cf3cf9be7159e580323ac0b51ad10ec2e181d1f777479b7983e7
Vendor states this is fixed in 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a (fixed)
Vendor states this is fixed in 46d59ff421824b6483549d87f14efffbbbd1f6cb (fixed)
Vendor states this is fixed in 6cd84cefd8b73e85b9eda17b319bd40a670f3a38 (fixed)
Vendor states this is fixed in 70a38f87bed7f0694fd07988b47b2db1e10d8df3 (fixed)
Vendor states this is fixed in 7ce4c23e783e766507b2cef27bbf97e9ca944f1a (fixed)
Vendor states this is fixed in 84008bf1860e0ef8059a7583a1163f36b704d08a (fixed)
Vendor states this is fixed in cb3420c047957e565101585bb4f15e1a6e3de6b0 (fixed)
Vendor states this is fixed in fe3b45b56b6c3d4b6b341de27fa291005287a21c (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card