{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89974 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89974 is a high-severity use after free 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-89974 and fix it if it is affected.\n\nWhat it is: CVE-2026-89974 is a high-severity use after free 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-89974 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-89974/ (Markdown: https://insights.sbomify.com/CVE-2026-89974/index.md)","id":"CVE-2026-89974","markdown":"https://insights.sbomify.com/CVE-2026-89974/index.md","name":"CVE-2026-89974","record":{"aliases":["BELL-CVE-2026-89974","DEBIAN-CVE-2026-89974","GHSA-6hqx-63gq-9x2p","UBUNTU-CVE-2026-89974"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NVMe driver","requires_auth":"none","summary":"A double free vulnerability in the Linux kernel NVMe FC driver allows attackers to cause a denial of service or potentially execute code via memory corruption.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/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\nnvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails\n\nnvmf_create_ctrl() owns the fabrics options and frees them whenever\n-\u003ecreate_ctrl() returns an error, so a transport must not free them on\nits own error paths.  nvme-fc tracks this by testing ctrl-\u003ectrl.opts in\nnvme_fc_ctrl_free(), which requires nvme_fc_init_ctrl() to clear that\npointer on every error exit.\n\nThe coupling is implicit, and commit 1a9e218195a5 (\"nvme: split device\nadd from initialization\") broke it by adding a second error exit.  When\nnvme_add_ctrl() fails, nvme_fc_init_ctrl() jumps to out_put_ctrl:, past\nthe \"ctrl-\u003ectrl.opts = NULL\" that only sits on the fail_ctrl: path, so\nnvme_fc_ctrl_free() frees the options and nvmf_create_ctrl() frees them\na second time:\n\n  BUG: KASAN: slab-use-after-free in nvmf_free_options+0x30/0x190\n   nvmf_free_options+0x30/0x190 drivers/nvme/host/fabrics.c:1284\n   nvmf_create_ctrl drivers/nvme/host/fabrics.c:1374 [inline]\n  Freed by task 5534:\n   nvme_fc_ctrl_free drivers/nvme/host/fc.c:2374 [inline]\n   nvme_fc_init_ctrl+0xe17/0x1450 drivers/nvme/host/fc.c:3605\n\nnvme_add_ctrl() fails when dev_set_name() cannot allocate, so this is\nreachable under memory pressure or fault injection.  Without KASAN the\noptions are freed twice.\n\nRather than clear the pointer on the second exit as well, derive\nownership the way nvme-tcp, nvme-rdma and nvme-loop do, from list\nmembership: their free_ctrl leaves the options alone unless the\ncontroller made it onto the transport list.\n\nThe list cannot simply be populated on the success path as it is there.\nnvme-fc runs the initial connect synchronously via flush_delayed_work(),\nand the controller has to be reachable on rport-\u003ectrl_list for the whole\nof it: nvme_fc_unregister_remoteport() needs to find it to signal\nconnectivity loss, nvme_fc_match_disconn_ls() matches an incoming\nDisconnect Association LS against ctrl-\u003eassociation_id, which is only\nassigned during that window, nvme_fc_resume_controller() needs it on\nremoteport re-registration, and nvme_fc_existing_controller() uses it to\nreject a duplicate connect racing the one in flight.\n\nKeep the insertion where it is and add a fail_unlist: label, falling\ninto fail_ctrl:, for the error paths that run after it.  The earlier\nerror paths never reach the insertion and keep using fail_ctrl:\ndirectly, so the list is only touched where the controller is actually\non it.\n\nnvme_fc_ctrl_free() cannot use the plain \"goto free_ctrl\" the other\ntransports use, because it still has to put_device(), release the rport\nreference and free the ida entry for resources taken before the\ninsertion.  Sample list_empty() under rport-\u003elock instead.\n\nctrl-\u003ectrl.opts also stays valid for the whole teardown now.  That is\nnot the bug being fixed, but it removes some fragility around the old\nidiom: nvme_free_ctrl() calls nvme_auth_free() before -\u003efree_ctrl(), and\nctrl_max_dhchaps() dereferences ctrl-\u003eopts without a NULL check when\nctrl-\u003edhchap_ctxs is set, which nvme-fc permits since NVMF_ALLOWED_OPTS\nallows the dhchap options.  The nvme sysfs attributes that dereference\nctrl-\u003eopts, such as hostnqn and address, evaluate their is_visible()\ntest once at device_add() time and stay readable until\ncdev_device_del().","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-fc: fix double free of fabrics options when nvme_add_ctrl() fails","id":"CVE-2026-89974","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":"nvme-fabrics: fix DHCHAP secret leak on parse failure","id":"CVE-2026-89975"},"packages":[],"prev":{"headline":"nvme-tcp: check the data direction of a C2HData PDU","id":"CVE-2026-89973"},"products":["Linux"],"published":"2026-09-16","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 double free vulnerability in the Linux kernel NVMe FC driver allows attackers to cause a denial of service or potentially execute code via memory corruption.","url":"https://insights.sbomify.com/CVE-2026-89974/"}