{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89539 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89539 is a memory corruption 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-89539 and fix it if it is affected.\n\nWhat it is: CVE-2026-89539 is a memory corruption 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-89539 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-89539/ (Markdown: https://insights.sbomify.com/CVE-2026-89539/index.md)","id":"CVE-2026-89539","markdown":"https://insights.sbomify.com/CVE-2026-89539/index.md","name":"CVE-2026-89539","record":{"aliases":["AZL-100665","BELL-CVE-2026-89539","DEBIAN-CVE-2026-89539","GHSA-j7j8-rmpg-46w5","UBUNTU-CVE-2026-89539"],"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 memory leak in the Linux kernel SUNRPC module by sending duplicate CREDS_VALUE options, leading to resource exhaustion.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nSUNRPC: reject duplicate CREDS_VALUE options\n\ngssx_dec_option_array() walks the wire-supplied option array and, for\nevery entry whose name matches CREDS_VALUE, calls\ngssx_dec_linux_creds() on the same struct svc_cred. That helper\nunconditionally installs a fresh groups_alloc() result into\ncreds-\u003ecr_group_info without releasing whatever pointer was already\nthere:\n\n    for (i = 0; i \u003c count; i++) {\n        ... decode name ...\n        if (length == sizeof(CREDS_VALUE) \u0026\u0026\n            memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {\n            err = gssx_dec_linux_creds(xdr, creds);\n            ...\n        }\n    }\n\nA reply that carries two CREDS_VALUE entries therefore overwrites\ncr_group_info on the second iteration and orphans the group_info\nallocated by the first call. The earlier free_creds path only\nreleases the last cr_group_info via free_svc_cred(), so the first\nallocation's refcount stays at one and its kvmalloc-backed storage\nis leaked. No in-tree caller of gssp_accept_sec_context_upcall()\nexpects more than one CREDS_VALUE per reply.\n\nFix by tracking whether a CREDS_VALUE option has already been\ndecoded and returning -EINVAL on any subsequent match, so the\nfree_creds path releases the single group_info that was installed.","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":"SUNRPC: reject duplicate CREDS_VALUE options","id":"CVE-2026-89539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"sunrpc: init gssp_lock before publishing proc entry","id":"CVE-2026-89540"},"packages":[],"prev":{"headline":"SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field","id":"CVE-2026-89538"},"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 memory leak in the Linux kernel SUNRPC module by sending duplicate CREDS_VALUE options, leading to resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-89539/"}