Review reviewHigh

CVE-2025-40171

Linux

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.

CVSS
7.5
EPSS
0.43%
35.4% percentile
CISA KEV
Not listed
Published
2025.11.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.43%
Technical severityCVSS 7.5

Vulnerability overview

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.

Affected product and versions

Product
Linux
Affected versions
>= 5e0bc09a52b6169ce90f7ac6e195791adb16cec4 < 11269c08013f4ee8b8f5edc6c56700acb34092d0, >= 9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8 < a28112cc55013cd8cbd5d36b5115a5b851151bd9, >= eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30 < 060ecc81240ef9d60d9485a3a5eb55a0d6e7a25c, >= 710c69dbaccdac312e32931abcb8499c1525d397 < 7331925c247b03b7767b8cd93cfe1b7aa2377850, >= 710c69dbaccdac312e32931abcb8499c1525d397 < 7a619f8c869117ffed08365b377f66b7e1d941b4, >= 710c69dbaccdac312e32931abcb8499c1525d397 < db5a5406fb7e5337a074385c7a3e53c77f2c1bd3, >= 1d86f79287206deec36d63b89c741cf542b6cadd, >= 5.15.150 < 5.15.195, >= 6.1.80 < 6.1.156, >= 6.6.19 < 6.6.112, >= 6.7.7 < 6.8, >= 6.8
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
Not available
CVE-2025-40171 — Linux | SECUFOCUS NOW