Answer in brief
CVE-2026-72219 records a Unknown severity vulnerability in lockd: Plug nlm_file leak when nlm_do_fopen() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72219 records a Unknown severity vulnerability in lockd: Plug nlm_file leak when nlm_do_fopen() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e580323ac0b51ad10ec2e181d1f777479b7983e7 <bca74fff138429f3d5802865f38fc883d53a4f1a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <d7c677feb3aa1f42b1026d75a8ea61338b51e4fb || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <39f59bf67231ed2eb0cdf6337194360e964b609a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <ddfbd816273b4e9c9b836f5b8773664c6f40f807 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <1403f1221a35a6caf959bb7bf005741f17263c66 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <1161c4b5bd0048c8148e919f818a33cff3623ef0 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <f16a1513452edb532fec81e591c64c320866719c || >=5.10.220 <5.10.261 | bca74fff138429f3d5802865f38fc883d53a4f1a, d7c677feb3aa1f42b1026d75a8ea61338b51e4fb, 39f59bf67231ed2eb0cdf6337194360e964b609a, ddfbd816273b4e9c9b836f5b8773664c6f40f807, 1403f1221a35a6caf959bb7bf005741f17263c66, 1161c4b5bd0048c8148e919f818a33cff3623ef0, 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9, f16a1513452edb532fec81e591c64c320866719c, 5.10.261 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e580323ac0b51ad10ec2e181d1f777479b7983e7 <bca74fff138429f3d5802865f38fc883d53a4f1a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <d7c677feb3aa1f42b1026d75a8ea61338b51e4fb || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <39f59bf67231ed2eb0cdf6337194360e964b609a || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <ddfbd816273b4e9c9b836f5b8773664c6f40f807 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <1403f1221a35a6caf959bb7bf005741f17263c66 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <1161c4b5bd0048c8148e919f818a33cff3623ef0 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 || >=7f024fcd5c97dc70bb9121c80407cf3cf9be7159 <f16a1513452edb532fec81e591c64c320866719c || >=5.10.220 <5.10.261 | bca74fff138429f3d5802865f38fc883d53a4f1a, d7c677feb3aa1f42b1026d75a8ea61338b51e4fb, 39f59bf67231ed2eb0cdf6337194360e964b609a, ddfbd816273b4e9c9b836f5b8773664c6f40f807, 1403f1221a35a6caf959bb7bf005741f17263c66, 1161c4b5bd0048c8148e919f818a33cff3623ef0, 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9, f16a1513452edb532fec81e591c64c320866719c, 5.10.261 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.