Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e580323ac0b51ad10ec2e181d1f777479b7983e7 – < bca74fff138429f3d5802865f38fc883d53a4f1a
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < d7c677feb3aa1f42b1026d75a8ea61338b51e4fb
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 39f59bf67231ed2eb0cdf6337194360e964b609a
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < ddfbd816273b4e9c9b836f5b8773664c6f40f807
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 1403f1221a35a6caf959bb7bf005741f17263c66
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 1161c4b5bd0048c8148e919f818a33cff3623ef0
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < 3f2dc01b9cb516d4727a3b9263ee58c71ca00ba9
    • affected 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 – < f16a1513452edb532fec81e591c64c320866719c
    • affected 5.10.220 – < 5.10.261
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72219 badge
[![CVE-2026-72219](https://cveledger.app/badge/CVE-2026-72219.svg)](https://cveledger.app/cve/CVE-2026-72219)

Record last updated .