{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97951 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97951 is a denial of service vulnerability in Linux, published on 25 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-97951 and fix it if it is affected.\n\nWhat it is: CVE-2026-97951 is a denial of service vulnerability in Linux, published on 25 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-97951 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-97951/ (Markdown: https://insights.sbomify.com/CVE-2026-97951/index.md)","id":"CVE-2026-97951","markdown":"https://insights.sbomify.com/CVE-2026-97951/index.md","name":"CVE-2026-97951","record":{"aliases":["AZL-110479","BELL-CVE-2026-97951","DEBIAN-CVE-2026-97951","GHSA-gmcj-g64q-4863","UBUNTU-CVE-2026-97951"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel iSCSI","requires_auth":"none","summary":"An attacker can cause a denial of service by aborting iSCSI write commands, leading to a kernel deadlock in the target worker thread.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nscsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands\n\nWhen a LUN_RESET aborts a WRITE command that is in the\nTRANSPORT_WRITE_PENDING state, the target core sets CMD_T_ABORTED and\nwaits for the frontend to finish processing.\n\nIf the initiator subsequently sends the remaining dataout PDUs,\n__iscsit_check_dataout_hdr() catches the payload, stops the dataout\ntimer if the sequence is final and finally dumps the data.  However, the\niSCSI target doesn't trigger the completion process for these aborted\ncommands. Because of this, the abort path hangs indefinitely in\ntarget_put_cmd_and_wait(), leading to a deadlocked target worker thread.\n\nFix this by explicitly calling target_complete_cmd() when the final\ndataout PDU is received for an aborted WRITE command.\ntarget_complete_cmd() detects the CMD_T_ABORTED flag and cleanly routes\nthe command into target_abort_work, allowing the abort completion to\nsuccessfully unblock.","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":"scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands","id":"CVE-2026-97951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"sunvdc: unmap LDC cookies when the descriptor send fails","id":"CVE-2026-97952"},"packages":[],"prev":{"headline":"configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry","id":"CVE-2026-97950"},"products":["Linux"],"published":"2026-09-25","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-19","vendors":["Linux"]},"summary":"An attacker can cause a denial of service by aborting iSCSI write commands, leading to a kernel deadlock in the target worker thread.","url":"https://insights.sbomify.com/CVE-2026-97951/"}