# CVE-2025-40171: nvmet-fc: move lsop put work to nvmet_fc_ls_req_op

> A reference counting bug in the Linux kernel's nvmet-fc driver can lead to resource leaks and potential denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 12 Nov 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-40171, DEBIAN-CVE-2025-40171, GHSA-j97x-pm24-3q67, ROOT-OS-DEBIAN-13-CVE-2025-40171, ROOT-OS-UBUNTU-2404-CVE-2025-40171, UBUNTU-CVE-2025-40171

## What is CVE-2025-40171?

CVE-2025-40171 is a high-severity denial of service vulnerability in Linux, published on 12 Nov 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:

nvmet-fc: move lsop put work to nvmet_fc_ls_req_op

It’s possible for more than one async command to be in flight from
__nvmet_fc_send_ls_req. For each command, a tgtport reference is taken.

In the current code, only one put work item is queued at a time, which
results in a leaked reference.

To fix this, move the work item to the nvmet_fc_ls_req_op struct, which
already tracks all resources related to the command.

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


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

Apply the vendor's patch.

## Is CVE-2025-40171 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40171 is a high-severity denial of service vulnerability in Linux, published on 12 Nov 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-40171 in the wild and no public exploit code.

Affected product: 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-40171/ (Markdown: https://insights.sbomify.com/CVE-2025-40171/index.md)
```

## Sources

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

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