lockd: Plug nlm_file leak when nlm_do_fopen() fails
Summary
| CVE | CVE-2026-72219 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:21:40 UTC |
| Updated | 2026-08-15 06:21:40 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected e580323ac0b51ad10ec2e181d1f777479b7983e7 bca74fff138429f3d5802865f38fc883d53a4f1a git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 d7c677feb3aa1f42b1026d75a8ea61338b51e4fb git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 39f59bf67231ed2eb0cdf6337194360e964b609a git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 ddfbd816273b4e9c9b836f5b8773664c6f40f807 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 1403f1221a35a6caf959bb7bf005741f17263c66 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 1161c4b5bd0048c8148e919f818a33cff3623ef0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 f16a1513452edb532fec81e591c64c320866719c git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.10.220 5.10.261 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.261 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.212 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/1161c4b5bd0048c8148e919f818a33cff3623ef0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/39f59bf67231ed2eb0cdf6337194360e964b609a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ddfbd816273b4e9c9b836f5b8773664c6f40f807 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d7c677feb3aa1f42b1026d75a8ea61338b51e4fb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f16a1513452edb532fec81e591c64c320866719c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bca74fff138429f3d5802865f38fc883d53a4f1a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1403f1221a35a6caf959bb7bf005741f17263c66 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.