CVE Catalog

CVE-2026-97951

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the iSCSI target subsystem has a hang for aborted WRITE_PENDING commands. When the initiator sends remaining dataout PDUs after abort, the target does not trigger completion, leading to a deadlocked worker thread. The fix calls target_complete_cmd() upon receiving the final dataout PDU.

Risk Assessment

Worker thread hang can lead to unresponsiveness of the iSCSI service, affecting availability of stored data. An attacker with access to iSCSI sessions can trigger this issue.

Recommendation

Apply a Linux kernel update containing the fix for iSCSI target. Restrict access to iSCSI sessions to trusted clients.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS