CVE-2026-97951

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

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2c9fa49e100f962af988f1c0529231bf14905cda5.0
Vendor states this is fixed in 19315262991dc983cc5c5c2ed24ff768abbf9339 (fixed)
Vendor states this is fixed in 37f7f54d06c6100511979d6e9c1222b404e3f006 (fixed)
Vendor states this is fixed in 638cf7c0cf64d5bb5704c3a78b54ae6602f69a32 (fixed)
Vendor states this is fixed in 9c777f8e0cb0486fdf16db8ffea32e562a31e85b (fixed)
Vendor states this is fixed in b070c8b4b237d55bdac13da3c5a994491177b312 (fixed)
Vendor states this is fixed in d5869dae5080e976d4b03cc33eb7ceb527f242bf (fixed)
Vendor states this is fixed in f6f6351e98c77c27b51763ef52deb2efe4b46ac7 (fixed)
Vendor states this is fixed in f806f54ae3de780b8f4139baefc95b81c599cf9f (fixed)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card