{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89484 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89484 is a vulnerability in Linux, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89484 and fix it if it is affected.\n\nWhat it is: CVE-2026-89484 is a vulnerability in Linux, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89484 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89484/ (Markdown: https://insights.sbomify.com/CVE-2026-89484/index.md)","id":"CVE-2026-89484","markdown":"https://insights.sbomify.com/CVE-2026-89484/index.md","name":"CVE-2026-89484","record":{"aliases":["AZL-100778","BELL-CVE-2026-89484","DEBIAN-CVE-2026-89484","GHSA-7hg8-pf72-7jmh","UBUNTU-CVE-2026-89484"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A remote attacker can cause a kernel crash via a null pointer dereference in the lockd module when lockowner allocation fails.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"lockd: fix NULL dereference on lockowner allocation failure","id":"CVE-2026-89484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"lockd: pin next file across nlm_inspect_file lock-drop","id":"CVE-2026-89485"},"packages":[],"prev":{"headline":"nvme: zero the discard fallback page","id":"CVE-2026-89483"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A remote attacker can cause a kernel crash via a null pointer dereference in the lockd module when lockowner allocation fails.","url":"https://insights.sbomify.com/CVE-2026-89484/"}