VulnerabilityPublished 15 Aug 2026Updated 6 Nov 2026

CVE-2026-72219: Linux kernel · lockd: Plug nlm_file leak when nlm_do_fopen() fails

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f16a1513452edb532fec81e591c64c320866719c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:19 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in f16a1513452edb532fec81e591c64c320866719c, ddfbd816273b4e9c9b836f5b8773664c6f40f807, d7c677feb3aa1f42b1026d75a8ea61338b51e4fb +6

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.10.220 <5.10.261	Fixed in f16a1513452edb532fec81e591c64c320866719c ddfbd816273b4e9c9b836f5b8773664c6f40f807 d7c677feb3aa1f42b1026d75a8ea61338b51e4fb bca74fff138429f3d5802865f38fc883d53a4f1a 1403f1221a35a6caf959bb7bf005741f17263c66 1161c4b5bd0048c8148e919f818a33cff3623ef0 39f59bf67231ed2eb0cdf6337194360e964b609a 5.10.261 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9
LinuxLinux	Affected =5.15	Fixed in–

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.

References

Community reviews

Loading reviews…