CVE-2025-38075: Linux kernel · scsi: target: iscsi: Fix timeout on deleted connection
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 5.15.0-1090.97~20.04.1 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1090.97~20.04.1, 5.15.0-1094.103~20.04.1, 5.15.0-1114.123~20.04.1 +60
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2025
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.
Patches and advisories
- ubuntu.com/security/notices/USN-7704-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7711-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7712-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7712-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7770-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7771-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix timeout on deleted connection NOPIN response timer may expire on a deleted connection and crash with such logs: Did not receive response to NOPIN on CID: 0, failing connection for I_T Nexus (null),i,0x00023d000125,iqn.2017-01.com.iscsi.target,t,0x3d BUG: Kernel NULL pointer dereference on read at 0x00000000 NIP strlcpy+0x8/0xb0 LR iscsit_fill_cxn_timeout_err_stats+0x5c/0xc0 [iscsi_target_mod] Call Trace: iscsit_handle_nopin_response_timeout+0xfc/0x120 [iscsi_target_mod] call_timer_fn+0x58/0x1f0 run_timer_softirq+0x740/0x860 __do_softirq+0x16c/0x420 irq_exit+0x188/0x1c0 timer_interrupt+0x184/0x410 That is because nopin response timer may be re-started on nopin timer expiration. Stop nopin timer before stopping the nopin response timer to be sure that no one of them will be re-started.
References
- ubuntu.com/security/CVE-2025-38075 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38075 (opens in a new tab)
- git.kernel.org/linus/7f533cc5ee4c4436cee51dc58e81dfd9c3384418 (opens in a new tab)
- git.kernel.org/stable/c/019ca2804f3fb49a7f8e56ea6aeaa1ff32724c27 (opens in a new tab)
- git.kernel.org/stable/c/2c5081439c7ab8da08427befe427f0d732ebc9f9 (opens in a new tab)
- git.kernel.org/stable/c/3e6429e3707943078240a2c0c0b3ee99ea9b0d9c (opens in a new tab)
- git.kernel.org/stable/c/571ce6b6f5cbaf7d24af03cad592fc0e2a54de35 (opens in a new tab)
- git.kernel.org/stable/c/6815846e0c3a62116a7da9740e3a7c10edc5c7e9 (opens in a new tab)
- git.kernel.org/stable/c/7f533cc5ee4c4436cee51dc58e81dfd9c3384418 (opens in a new tab)
- git.kernel.org/stable/c/87389bff743c55b6b85282de91109391f43e0814 (opens in a new tab)
- git.kernel.org/stable/c/fe8421e853ef289e1324fcda004751c89dd9c18a (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7711-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7712-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7704-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7712-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-1 (opens in a new tab)