# CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection

> A null pointer dereference in the Linux kernel iSCSI target module can cause a system crash when a NOPIN response timer expires on a deleted connection.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jun 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-64043, BELL-CVE-2025-38075, DEBIAN-CVE-2025-38075, GHSA-qr73-mcp4-c9g4, ROOT-OS-DEBIAN-11-CVE-2025-38075, ROOT-OS-DEBIAN-12-CVE-2025-38075, ROOT-OS-UBUNTU-2204-CVE-2025-38075, ROOT-OS-UBUNTU-2404-CVE-2025-38075, UBUNTU-CVE-2025-38075

## What is CVE-2025-38075?

CVE-2025-38075 is a critical vulnerability in Debian Debian Linux, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-38075?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-38075?

Apply the vendor's patch.

## Is CVE-2025-38075 being exploited?

There is no known exploitation of CVE-2025-38075 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38075 and fix it if it is affected.

What it is: CVE-2025-38075 is a critical vulnerability in Debian Debian Linux, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-38075 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-38075/ (Markdown: https://insights.sbomify.com/CVE-2025-38075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38075
- OSV: https://osv.dev/vulnerability/CVE-2025-38075

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-38075/
Summaries are generated and may contain mistakes; the official description above is the record.