CVE-2026-97951: Linux kernel · scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f806f54ae3de780b8f4139baefc95b81c599cf9f : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f806f54ae3de780b8f4139baefc95b81c599cf9f, f6f6351e98c77c27b51763ef52deb2efe4b46ac7, d5869dae5080e976d4b03cc33eb7ceb527f242bf +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This issue has been fixed in the Linux kernel. Users should update to a fixed kernel version containing the commits identified by the provided fixedVersions hashes. No additional mitigation is required once the patch is applied.
Description
A vulnerability in the Linux kernel's iSCSI target implementation caused a hang when WRITE_PENDING commands aborted by a LUN_RESET were not properly completed. This led to a deadlock in the target worker thread due to the abort path hanging indefinitely. The issue was fixed by ensuring that aborted WRITE commands trigger the completion process correctly.
References
- git.kernel.org/stable/c/b070c8b4b237d55bdac13da3c5a994491177b312 (opens in a new tab)
- git.kernel.org/stable/c/19315262991dc983cc5c5c2ed24ff768abbf9339 (opens in a new tab)
- git.kernel.org/stable/c/f806f54ae3de780b8f4139baefc95b81c599cf9f (opens in a new tab)
- git.kernel.org/stable/c/9c777f8e0cb0486fdf16db8ffea32e562a31e85b (opens in a new tab)
- git.kernel.org/stable/c/638cf7c0cf64d5bb5704c3a78b54ae6602f69a32 (opens in a new tab)
- git.kernel.org/stable/c/f6f6351e98c77c27b51763ef52deb2efe4b46ac7 (opens in a new tab)
- git.kernel.org/stable/c/37f7f54d06c6100511979d6e9c1222b404e3f006 (opens in a new tab)
- git.kernel.org/stable/c/d5869dae5080e976d4b03cc33eb7ceb527f242bf (opens in a new tab)