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-89484

lockd: fix NULL dereference on lockowner allocation failure

Description

In the Linux kernel, the following vulnerability has been resolved: lockd: fix NULL dereference on lockowner allocation failure nlmclnt_locks_init_private() installs NLM file lock operations even when nlmclnt_find_lockowner() fails to allocate a lockowner. nlmclnt_proc() then returns -ENOMEM, but the VFS still tears down the partially initialized file_lock and calls locks_release_private(). That invokes nlmclnt_locks_release_private(), which dereferences fl->fl_u.nfs_fl.owner and crashes because the owner was never installed. Clear fl_ops before attempting to initialize the NLM private state, and install the NLM lock operations only after a lockowner has been allocated successfully.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 49 days 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.21% · top 88% of all CVEs (11 Nov 2026)
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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b61053a3795c2913a7af3ab6218acfdaf52fcafe
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6db5af172ccc3223c8f730a9a4212f6427feee3e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 07adfbb3de7529f58ca708a97ead7fa4fdb71056
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d662f7fc04fde305a27f304b3cd19b614d366839
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 51af080ca4e553256c59a75a877b9b4fff828311
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4c7fc129db061c7daab841c4f3c342d894832362
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .