Strix
56.9K

CVE-2026-72218

UnknownEPSS 0.21%

Last modified

CVE-2026-72218 is a vulnerability of currently unknown severity. 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(). EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e580323ac0b51ad10ec2e181d1f777479b7983e7, < 6cd84cefd8b73e85b9eda17b319bd40a670f3a38; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < fe3b45b56b6c3d4b6b341de27fa291005287a21c; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < cb3420c047957e565101585bb4f15e1a6e3de6b0; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 7ce4c23e783e766507b2cef27bbf97e9ca944f1a; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 84008bf1860e0ef8059a7583a1163f36b704d08a; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 46d59ff421824b6483549d87f14efffbbbd1f6cb; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 70a38f87bed7f0694fd07988b47b2db1e10d8df3; >= 5.10.220, < 5.10.261
LinuxLinux5.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72218?
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.
How severe is CVE-2026-72218?
Severity scoring for CVE-2026-72218 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72218?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72218?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST