{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89975 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89975 is a memory corruption vulnerability in Linux, published on 16 Sep 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-89975 and fix it if it is affected.\n\nWhat it is: CVE-2026-89975 is a memory corruption vulnerability in Linux, published on 16 Sep 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-89975 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-89975/ (Markdown: https://insights.sbomify.com/CVE-2026-89975/index.md)","id":"CVE-2026-89975","markdown":"https://insights.sbomify.com/CVE-2026-89975/index.md","name":"CVE-2026-89975","record":{"aliases":["AZL-101645","BELL-CVE-2026-89975","DEBIAN-CVE-2026-89975","GHSA-9hxp-3v8h-pjp2","UBUNTU-CVE-2026-89975"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a memory leak of sensitive DHCHAP secrets in the Linux kernel NVMe fabrics driver, potentially causing denial of service or secret exposure.","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\nnvme-fabrics: fix DHCHAP secret leak on parse failure\n\nnvmf_parse_options() duplicates dhchap_secret and dhchap_ctrl_secret\nwith match_strdup() before validating the DHHC-1: representation.\n\nIf validation fails, the parser returns -EINVAL before the temporary\nstring in p is assigned to opts-\u003edhchap_secret or\nopts-\u003edhchap_ctrl_secret. nvmf_create_ctrl() subsequently frees opts,\nbut nvmf_free_options() cannot release the unassigned temporary string.\nEach rejected option therefore leaks one allocation.\n\nThis is easy to miss because valid secrets transfer ownership to opts\nand are freed normally, while the malformed-secret path still returns\nthe expected -EINVAL to userspace.\n\nWith CONFIG_NVME_HOST_AUTH enabled, the leak is reachable before the\nrequired-option checks and transport lookup. No NVMe-oF target or\nworking transport connection is required; for example, repeatedly\nwriting\n\n\tdhchap_secret=BAD\n\nor\n\n\tdhchap_ctrl_secret=BAD\n\nto /dev/nvme-fabrics deterministically takes the leaking parse path.\n\nFree the temporary string before leaving both validation error paths.\nUse kfree_sensitive() because the copied option may contain secret\nmaterial even when its representation is rejected, matching the\nsensitive cleanup used for stored DHCHAP secrets.","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":"nvme-fabrics: fix DHCHAP secret leak on parse failure","id":"CVE-2026-89975","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":"accel/ethosu: fix job completion fence cleanup","id":"CVE-2026-89976"},"packages":[],"prev":{"headline":"nvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails","id":"CVE-2026-89974"},"products":["Linux"],"published":"2026-09-16","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 local attacker can trigger a memory leak of sensitive DHCHAP secrets in the Linux kernel NVMe fabrics driver, potentially causing denial of service or secret exposure.","url":"https://insights.sbomify.com/CVE-2026-89975/"}