CVE-2026-72219
lockd: Plug nlm_file leak when nlm_do_fopen() fails
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5.10.220 · fixed in 5.10.261
- Linux Linux
5.15
References 8
git.kernel.org
- stable/c/bca74fff138429f3d5802865f38fc883d53a4f1a
- stable/c/d7c677feb3aa1f42b1026d75a8ea61338b51e4fb
- stable/c/39f59bf67231ed2eb0cdf6337194360e964b609a
- stable/c/ddfbd816273b4e9c9b836f5b8773664c6f40f807
- stable/c/1403f1221a35a6caf959bb7bf005741f17263c66
- stable/c/1161c4b5bd0048c8148e919f818a33cff3623ef0
- stable/c/3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9
- stable/c/f16a1513452edb532fec81e591c64c320866719c