{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22989 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-22989 is a medium-severity vulnerability in Linux kernel, published on 23 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22989 and fix it if it is affected.\n\nWhat it is: CVE-2026-22989 is a medium-severity vulnerability in Linux kernel, published on 23 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-22989 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-22989/ (Markdown: https://insights.sbomify.com/CVE-2026-22989/index.md)","id":"CVE-2026-22989","markdown":"https://insights.sbomify.com/CVE-2026-22989/index.md","name":"CVE-2026-22989","record":{"aliases":["BELL-CVE-2026-22989","DEBIAN-CVE-2026-22989","GHSA-rph5-qwhf-vw4p","ROOT-OS-DEBIAN-13-CVE-2026-22989","UBUNTU-CVE-2026-22989"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NFS","requires_auth":"low_privilege","summary":"A local attacker can crash the NFS server by triggering a null pointer dereference when unlocking the filesystem while the server is not running.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: check that server is running in unlock_filesystem\n\nIf we are trying to unlock the filesystem via an administrative\ninterface and nfsd isn't running, it crashes the server. This\nhappens currently because nfsd4_revoke_states() access state\nstructures (eg., conf_id_hashtbl) that has been freed as a part\nof the server shutdown.\n\n[   59.465072] Call trace:\n[   59.465308]  nfsd4_revoke_states+0x1b4/0x898 [nfsd] (P)\n[   59.465830]  write_unlock_fs+0x258/0x440 [nfsd]\n[   59.466278]  nfsctl_transaction_write+0xb0/0x120 [nfsd]\n[   59.466780]  vfs_write+0x1f0/0x938\n[   59.467088]  ksys_write+0xfc/0x1f8\n[   59.467395]  __arm64_sys_write+0x74/0xb8\n[   59.467746]  invoke_syscall.constprop.0+0xdc/0x1e8\n[   59.468177]  do_el0_svc+0x154/0x1d8\n[   59.468489]  el0_svc+0x40/0xe0\n[   59.468767]  el0t_64_sync_handler+0xa0/0xe8\n[   59.469138]  el0t_64_sync+0x1ac/0x1b0\n\nEnsure this can't happen by taking the nfsd_mutex and checking that\nthe server is still up, and then holding the mutex across the call to\nnfsd4_revoke_states().","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":"nfsd: check that server is running in unlock_filesystem","id":"CVE-2026-22989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"libceph: replace overzealous BUG_ON in osdmap_apply_incremental()","id":"CVE-2026-22990"},"packages":[],"prev":{"headline":"arp: do not assume dev_hard_header() does not change skb-\u003ehead","id":"CVE-2026-22988"},"products":["Linux"],"published":"2026-01-23","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can crash the NFS server by triggering a null pointer dereference when unlocking the filesystem while the server is not running.","url":"https://insights.sbomify.com/CVE-2026-22989/"}