Answer in brief
CVE-2025-38075 records a Unknown severity vulnerability in scsi: target: iscsi: Fix timeout on deleted connection. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38075 records a Unknown severity vulnerability in scsi: target: iscsi: Fix timeout on deleted connection. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e48354ce078c079996f89d715dfa44814b4eba01 <571ce6b6f5cbaf7d24af03cad592fc0e2a54de35 || >=e48354ce078c079996f89d715dfa44814b4eba01 <2c5081439c7ab8da08427befe427f0d732ebc9f9 || >=e48354ce078c079996f89d715dfa44814b4eba01 <019ca2804f3fb49a7f8e56ea6aeaa1ff32724c27 || >=e48354ce078c079996f89d715dfa44814b4eba01 <6815846e0c3a62116a7da9740e3a7c10edc5c7e9 || >=e48354ce078c079996f89d715dfa44814b4eba01 <fe8421e853ef289e1324fcda004751c89dd9c18a || >=e48354ce078c079996f89d715dfa44814b4eba01 <87389bff743c55b6b85282de91109391f43e0814 || >=e48354ce078c079996f89d715dfa44814b4eba01 <3e6429e3707943078240a2c0c0b3ee99ea9b0d9c || >=e48354ce078c079996f89d715dfa44814b4eba01 <7f533cc5ee4c4436cee51dc58e81dfd9c3384418 | 571ce6b6f5cbaf7d24af03cad592fc0e2a54de35, 2c5081439c7ab8da08427befe427f0d732ebc9f9, 019ca2804f3fb49a7f8e56ea6aeaa1ff32724c27, 6815846e0c3a62116a7da9740e3a7c10edc5c7e9, fe8421e853ef289e1324fcda004751c89dd9c18a, 87389bff743c55b6b85282de91109391f43e0814, 3e6429e3707943078240a2c0c0b3ee99ea9b0d9c, 7f533cc5ee4c4436cee51dc58e81dfd9c3384418 |
| Linux/Linuxgeneric | 3.1 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e48354ce078c079996f89d715dfa44814b4eba01 <571ce6b6f5cbaf7d24af03cad592fc0e2a54de35 || >=e48354ce078c079996f89d715dfa44814b4eba01 <2c5081439c7ab8da08427befe427f0d732ebc9f9 || >=e48354ce078c079996f89d715dfa44814b4eba01 <019ca2804f3fb49a7f8e56ea6aeaa1ff32724c27 || >=e48354ce078c079996f89d715dfa44814b4eba01 <6815846e0c3a62116a7da9740e3a7c10edc5c7e9 || >=e48354ce078c079996f89d715dfa44814b4eba01 <fe8421e853ef289e1324fcda004751c89dd9c18a || >=e48354ce078c079996f89d715dfa44814b4eba01 <87389bff743c55b6b85282de91109391f43e0814 || >=e48354ce078c079996f89d715dfa44814b4eba01 <3e6429e3707943078240a2c0c0b3ee99ea9b0d9c || >=e48354ce078c079996f89d715dfa44814b4eba01 <7f533cc5ee4c4436cee51dc58e81dfd9c3384418 | 571ce6b6f5cbaf7d24af03cad592fc0e2a54de35, 2c5081439c7ab8da08427befe427f0d732ebc9f9, 019ca2804f3fb49a7f8e56ea6aeaa1ff32724c27, 6815846e0c3a62116a7da9740e3a7c10edc5c7e9, fe8421e853ef289e1324fcda004751c89dd9c18a, 87389bff743c55b6b85282de91109391f43e0814, 3e6429e3707943078240a2c0c0b3ee99ea9b0d9c, 7f533cc5ee4c4436cee51dc58e81dfd9c3384418 |
| Linux/Linuxgeneric | 3.1 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.