Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a, 46d59ff421824b6483549d87f14efffbbbd1f6cb, 5.10.261.

Low priority for now. Upgrade to Linux Linux 3a5c55a19cad62f2973be25fe96a1a9e7f618e8a, 46d59ff421824b6483549d87f14efffbbbd1f6cb, 5.10.261 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72218

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • e580323ac0b51ad10ec2e181d1f777479b7983e7 and later · before 6cd84cefd8b73e85b9eda17b319bd40a670f3a38affected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before fe3b45b56b6c3d4b6b341de27fa291005287a21caffected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before cb3420c047957e565101585bb4f15e1a6e3de6b0affected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before 7ce4c23e783e766507b2cef27bbf97e9ca944f1aaffected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before 84008bf1860e0ef8059a7583a1163f36b704d08aaffected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before 46d59ff421824b6483549d87f14efffbbbd1f6cbaffected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before 3a5c55a19cad62f2973be25fe96a1a9e7f618e8aaffected · git
    • 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 and later · before 70a38f87bed7f0694fd07988b47b2db1e10d8df3affected · git
    • 5.10.220 and later · before 5.10.261affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72216Aug 15, 2026 · remoteproc: qcom: Fix leak when custom dump_segments addition fails
    0Monitor
  • ← EarlierCVE-2026-72217Aug 15, 2026 · SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing
    39Monitor
  • Later →CVE-2026-72219Aug 15, 2026 · lockd: Plug nlm_file leak when nlm_do_fopen() fails
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3a5c55a19cad62f2973be25fe96a1a9e7f618e8aVendor (CNA)
Linux Linux46d59ff421824b6483549d87f14efffbbbd1f6cbVendor (CNA)
Linux Linux5.10.261Vendor (CNA)
Linux Linux6cd84cefd8b73e85b9eda17b319bd40a670f3a38Vendor (CNA)
Linux Linux70a38f87bed7f0694fd07988b47b2db1e10d8df3Vendor (CNA)
Linux Linux7ce4c23e783e766507b2cef27bbf97e9ca944f1aVendor (CNA)
Linux Linux84008bf1860e0ef8059a7583a1163f36b704d08aVendor (CNA)
Linux Linuxcb3420c047957e565101585bb4f15e1a6e3de6b0Vendor (CNA)
Linux Linuxfe3b45b56b6c3d4b6b341de27fa291005287a21cVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records