CVE-2026-72219
Last modified
CVE-2026-72219 is a vulnerability of currently unknown severity. 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[]. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e580323ac0b51ad10ec2e181d1f777479b7983e7, < bca74fff138429f3d5802865f38fc883d53a4f1a; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < d7c677feb3aa1f42b1026d75a8ea61338b51e4fb; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 39f59bf67231ed2eb0cdf6337194360e964b609a; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < ddfbd816273b4e9c9b836f5b8773664c6f40f807; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 1403f1221a35a6caf959bb7bf005741f17263c66; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 1161c4b5bd0048c8148e919f818a33cff3623ef0; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9; >= 7f024fcd5c97dc70bb9121c80407cf3cf9be7159, < f16a1513452edb532fec81e591c64c320866719c; >= 5.10.220, < 5.10.261 |
| Linux | Linux | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72219?
How severe is CVE-2026-72219?
How do I fix CVE-2026-72219?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72213In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72214In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72216In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72217In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72218In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7222A vulnerability was determined in code-projects Coaching Man…3.5
- CVE-2026-72220In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72221In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72222In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72223In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72224In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-72219?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
