GHSA-7HG8-PF72-7JMH
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-89484"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:30Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: fix NULL dereference on lockowner allocation failure\n\nnlmclnt_locks_init_private() installs NLM file lock operations even when\nnlmclnt_find_lockowner() fails to allocate a lockowner. nlmclnt_proc()\nthen returns -ENOMEM, but the VFS still tears down the partially\ninitialized file_lock and calls locks_release_private().\n\nThat invokes nlmclnt_locks_release_private(), which dereferences\nfl-\u003efl_u.nfs_fl.owner and crashes because the owner was never installed.\n\nClear fl_ops before attempting to initialize the NLM private state, and\ninstall the NLM lock operations only after a lockowner has been allocated\nsuccessfully.",
"id": "GHSA-7hg8-pf72-7jmh",
"modified": "2026-09-11T21:31:28Z",
"published": "2026-09-11T21:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89484"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/07adfbb3de7529f58ca708a97ead7fa4fdb71056"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4c7fc129db061c7daab841c4f3c342d894832362"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/51af080ca4e553256c59a75a877b9b4fff828311"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d662f7fc04fde305a27f304b3cd19b614d366839"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.