CVE-2026-97951

UnknownEPSS 0.18%

Last modified

CVE-2026-97951 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.18%

6.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2c9fa49e100f962af988f1c0529231bf14905cda, < b070c8b4b237d55bdac13da3c5a994491177b312; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < 19315262991dc983cc5c5c2ed24ff768abbf9339; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < f806f54ae3de780b8f4139baefc95b81c599cf9f; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < 9c777f8e0cb0486fdf16db8ffea32e562a31e85b; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < 638cf7c0cf64d5bb5704c3a78b54ae6602f69a32; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < f6f6351e98c77c27b51763ef52deb2efe4b46ac7; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < 37f7f54d06c6100511979d6e9c1222b404e3f006; >= 2c9fa49e100f962af988f1c0529231bf14905cda, < d5869dae5080e976d4b03cc33eb7ceb527f242bf
LinuxLinux5.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97951?
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.
How severe is CVE-2026-97951?
Severity scoring for CVE-2026-97951 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-97951?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97951?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST