CVE-2026-72219

lockd: Plug nlm_file leak when nlm_do_fopen() fails

N/A
Published: August 15, 2026 at 05:54 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.220 ≤ v < 5.10.2615.15 ≤ v < 5.15.2125.15 ≤ v < 6.1.1785.15 ≤ v < 6.12.975.15 ≤ v < 6.18.405.15 ≤ v < 6.6.1455.15 ≤ v < 7.1.55.15 ≤ v < 7.25.10.2205.157f024fcd5c97dc70bb9121c80407cf3cf9be7159e580323ac0b51ad10ec2e181d1f777479b7983e7
Vendor states this is fixed in 1161c4b5bd0048c8148e919f818a33cff3623ef0 (fixed)
Vendor states this is fixed in 1403f1221a35a6caf959bb7bf005741f17263c66 (fixed)
Vendor states this is fixed in 39f59bf67231ed2eb0cdf6337194360e964b609a (fixed)
Vendor states this is fixed in 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9 (fixed)
Vendor states this is fixed in bca74fff138429f3d5802865f38fc883d53a4f1a (fixed)
Vendor states this is fixed in d7c677feb3aa1f42b1026d75a8ea61338b51e4fb (fixed)
Vendor states this is fixed in ddfbd816273b4e9c9b836f5b8773664c6f40f807 (fixed)
Vendor states this is fixed in f16a1513452edb532fec81e591c64c320866719c (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card