scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands (CVE-2026-97951) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97951

scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands

Answer in brief

CVE-2026-97951 records a Unknown severity vulnerability in scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <638cf7c0cf64d5bb5704c3a78b54ae6602f69a32 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f6f6351e98c77c27b51763ef52deb2efe4b46ac7 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <37f7f54d06c6100511979d6e9c1222b404e3f006 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d5869dae5080e976d4b03cc33eb7ceb527f242bf \|\| >=0 <6.12.111 \|\| >=0 <6.18.53 \|\| >=0 <7.2.7	638cf7c0cf64d5bb5704c3a78b54ae6602f69a32, f6f6351e98c77c27b51763ef52deb2efe4b46ac7, 37f7f54d06c6100511979d6e9c1222b404e3f006, d5869dae5080e976d4b03cc33eb7ceb527f242bf, 6.12.111, 6.18.53, 7.2.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to 638cf7c0cf64d5bb5704c3a78b54ae6602f69a32 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands When a LUN_RESET aborts a WRITE command that is in the TRANSPORT_WRITE_PENDING state, the target core sets CMD_T_ABORTED and waits for the frontend to finish processing. If the initiator subsequently sends the remaining dataout PDUs, __iscsit_check_dataout_hdr() catches the payload, stops the dataout timer if the sequence is final and finally dumps the data. However, the iSCSI target doesn't trigger the completion process for these aborted commands. Because of this, the abort path hangs indefinitely in target_put_cmd_and_wait(), leading to a deadlocked target worker thread. Fix this by explicitly calling target_complete_cmd() when the final dataout PDU is received for an aborted WRITE command. target_complete_cmd() detects the CMD_T_ABORTED flag and cleanly routes the command into target_abort_work, allowing the abort completion to successfully unblock.

Quoted source text, attributed separately from HOL analysis.