Skip to main content
VulnerabilityPublished Updated

CVE-2026-89484: Linux kernel · lockd: fix NULL dereference on lockowner allocation failure

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d662f7fc04fde305a27f304b3cd19b614d366839 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d662f7fc04fde305a27f304b3cd19b614d366839, 51af080ca4e553256c59a75a877b9b4fff828311, 07adfbb3de7529f58ca708a97ead7fa4fdb71056 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d662f7fc04fde305a27f304b3cd19b614d366839
Fixed in
  • d662f7fc04fde305a27f304b3cd19b614d366839
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 51af080ca4e553256c59a75a877b9b4fff828311
Fixed in
  • 51af080ca4e553256c59a75a877b9b4fff828311
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 07adfbb3de7529f58ca708a97ead7fa4fdb71056
Fixed in
  • 07adfbb3de7529f58ca708a97ead7fa4fdb71056
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 6db5af172ccc3223c8f730a9a4212f6427feee3e
Fixed in
  • 6db5af172ccc3223c8f730a9a4212f6427feee3e
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4c7fc129db061c7daab841c4f3c342d894832362
Fixed in
  • 4c7fc129db061c7daab841c4f3c342d894832362
LinuxLinuxAffected
  • =2.6.12
Fixed in–

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.

References

Community reviews

Loading reviews…