{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89660 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89660 is a critical use after free 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-89660 and fix it if it is affected.\n\nWhat it is: CVE-2026-89660 is a critical use after free 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-89660 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-89660/ (Markdown: https://insights.sbomify.com/CVE-2026-89660/index.md)","id":"CVE-2026-89660","markdown":"https://insights.sbomify.com/CVE-2026-89660/index.md","name":"CVE-2026-89660","record":{"aliases":["BELL-CVE-2026-89660","DEBIAN-CVE-2026-89660","GHSA-xcq6-xf9g-6gc6","UBUNTU-CVE-2026-89660"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NFS","requires_auth":"none","summary":"A race condition in the Linux kernel's NFS server allows a use-after-free during client state revocation, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Prevent client use-after-free during admin state revocation\n\nA stateid holds only a bare pointer to its nfs4_client; a stateid\nreference does not pin it.  The client survives only because\n__destroy_client() drains its stateids before free_client() runs.\n\nnfsd4_revoke_states() drops nn-\u003eclient_lock across revoke_one_stid(),\nwhich dereferences the client to revoke a stateid and read\nclp-\u003ecl_minorversion.  A teardown racing the dropped lock can free\nthe client first.\n\nPinning cl_rpc_users under client_lock blocks the DESTROY_CLIENTID and\nEXCHANGE_ID teardown, which refuses while cl_rpc_users is non-zero.\nforce_expire_client() ignores it: once its wait for cl_rpc_users to\nreach zero has passed, a later pin goes unnoticed.\n\nUnder client_lock, skip a client whose cl_time is already zero --\nforce_expire_client() clears it there before waiting -- otherwise pin\ncl_rpc_users before dropping the lock.  The walk then either sees the\nexpiry and skips, or pins in time for that wait to cover the revoke.","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: Prevent client use-after-free during admin state revocation","id":"CVE-2026-89660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"NFSD: Prevent post-shutdown use-after-free in unlock_filesystem","id":"CVE-2026-89661"},"packages":[],"prev":{"headline":"NFSD: Prevent client use-after-free during delegation revoke","id":"CVE-2026-89659"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's NFS server allows a use-after-free during client state revocation, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-89660/"}