CVE-2026-72219
Received Received - Intake

BaseFortify

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
CVE-2026-72219
EUVD
EUVD-2026-59118

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a memory leak in the lockd component. When a client presents file handles that are rejected by the underlying export, the nlm_do_fopen() function fails. This failure path does not free the allocated nlm_file structure, causing a leak of one nlm_file per failure.

Detection Guidance

This vulnerability involves a memory leak in the Linux kernel's lockd component when nlm_do_fopen() fails. Detection requires checking for leaked nlm_file structures, which may manifest as increasing memory usage over time. Monitor kernel memory usage with commands like 'free -m' or 'cat /proc/meminfo' and watch for unusual growth. Check lockd-related processes with 'ps aux | grep lockd' and inspect kernel logs for errors with 'dmesg | grep lockd'.

Impact Analysis

The vulnerability can lead to resource exhaustion on the system running the affected Linux kernel. Repeated exploitation could deplete memory, causing performance degradation or system crashes due to lack of available memory for other processes.

Mitigation Strategies

Apply the latest Linux kernel patches to resolve the nlm_file leak. If immediate patching is not possible, consider disabling the lockd service temporarily with 'systemctl stop nlockd' or 'systemctl disable nlockd' to reduce exposure. Monitor system memory usage closely and restart affected services if leaks are detected.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72219. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart