CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection
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.
Security readout for executives and security teams
Plain-English summary
A timing flaw in the Linux kernel iSCSI target can leave a response timer running after its connection is deleted. When that timer expires, the kernel may dereference invalid data and crash, disrupting storage services and potentially the host. The supplied record rates it critical, although the described failure demonstrates availability impact rather than confidentiality or integrity compromise.
Executive priority
Treat affected, network-accessible iSCSI target hosts as urgent patching candidates because a kernel crash could interrupt storage and dependent business services. Avoid assuming data theft or modification from the CVSS score alone; the supplied technical evidence specifically supports denial of service. Validate actual component use before broad emergency action.
Technical view
The iSCSI target NOP-IN response timer can be restarted when the NOP-IN timer expires. During connection deletion, the response timer may consequently execute against a removed connection, reaching iscsit_fill_cxn_timeout_err_stats and causing a NULL-pointer dereference. The kernel fix stops the NOP-IN timer before stopping its response timer, preventing either timer from being restarted during teardown.
Likely exposure
Exposure is concentrated in Linux systems operating the kernel iSCSI target functionality, especially where iSCSI services are network-reachable. Systems not using this target component are unlikely to encounter the described path. The supplied affected-version data is ambiguous, so administrators should map distribution kernels to vendor advisories or referenced stable fixes.
Exploitation context
The supplied record reports CVSS 9.8 with network access, low complexity, no privileges, and no user interaction. However, it provides no proof of active exploitation, and the KEV indicator is false. The described outcome is a kernel crash arising from connection teardown and timer behavior; reliable attacker control is not established by these sources.
Researcher notes
The failure is a teardown race involving two related timers, not a generic iSCSI parsing flaw. The trace places the NULL dereference in timeout-error statistics handling after connection deletion. Stable-kernel commits document the timer shutdown ordering change. The bundle does not establish exploit reliability, attacker-controlled memory corruption, or confidentiality and integrity consequences despite the supplied CVSS vector.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced iSCSI timer-ordering fix.
Prioritize internet-facing or untrusted-network iSCSI target hosts.
Restrict iSCSI access to required initiators and trusted network segments.
If immediate updating is impossible, consider disabling unused iSCSI target functionality.
Consult distribution guidance before treating listed version labels as definitive fix boundaries.
Validation and detection
Inventory hosts loading or configuring the Linux iSCSI target component.
Identify kernel package versions and compare them with distribution security advisories.
Confirm the installed kernel incorporates the applicable referenced stable commit.
Review kernel logs for NOP-IN timeout messages and NULL-pointer crashes.
After updating, reboot into the corrected kernel and verify its running version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.