Public vulnerability disclosure

CVE-2026-72219

lockd: Plug nlm_file leak when nlm_do_fopen() fails

published

In the Linux kernel, the following vulnerability has been resolved: lockd: Plug nlm_file leak when nlm_do_fopen() fails A client can repeatedly drive nlm_do_fopen() failures by presenting file handles that the underlying export rejects. After kzalloc_obj() succeeds in nlm_lookup_file(), the freshly allocated nlm_file is not yet inserted into nlm_files[]. The nlm_do_fopen() failure path jumps to out_unlock, which releases nlm_file_mutex and returns without freeing the allocation, so each failure leaks one nlm_file. Route the failure through out_free so kfree() runs before the function returns.

Technical severityUnscoredNo score in collected sources
Published2026-08-15Source updated 2026-11-06
Collected2026-11-062 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ e580323ac0b51ad10ec2e181d1f777479b7983e7; < bca74fff138429f3d5802865f38fc883d53a4f1a (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < d7c677feb3aa1f42b1026d75a8ea61338b51e4fb (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 39f59bf67231ed2eb0cdf6337194360e964b609a (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < ddfbd816273b4e9c9b836f5b8773664c6f40f807 (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 1403f1221a35a6caf959bb7bf005741f17263c66 (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 1161c4b5bd0048c8148e919f818a33cff3623ef0 (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 (affected, git)
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159; < f16a1513452edb532fec81e591c64c320866719c (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

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/cves
https://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.

Agent access JSON · OpenAPI · CVE API guide