Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40171, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Deferred3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.48% · top 58% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 5e0bc09a52b6169ce90f7ac6e195791adb16cec4 – < 11269c08013f4ee8b8f5edc6c56700acb34092d0
    • affected 9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8 – < a28112cc55013cd8cbd5d36b5115a5b851151bd9
    • affected eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30 – < 060ecc81240ef9d60d9485a3a5eb55a0d6e7a25c
    • affected 710c69dbaccdac312e32931abcb8499c1525d397 – < 7331925c247b03b7767b8cd93cfe1b7aa2377850
    • affected 710c69dbaccdac312e32931abcb8499c1525d397 – < 7a619f8c869117ffed08365b377f66b7e1d941b4
    • affected 710c69dbaccdac312e32931abcb8499c1525d397 – < db5a5406fb7e5337a074385c7a3e53c77f2c1bd3
    • affected 1d86f79287206deec36d63b89c741cf542b6cadd
    • affected 5.15.150 – < 5.15.195
    • affected 6.1.80 – < 6.1.156
    • affected 6.6.19 – < 6.6.112
    • affected 6.7.7 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 5.15.195 – ≤ 5.15.*
    • unaffected 6.1.156 – ≤ 6.1.*
    • unaffected 6.6.112 – ≤ 6.6.*
    • unaffected 6.12.53 – ≤ 6.12.*
    • unaffected 6.17.3 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40171 badge
[![CVE-2025-40171](https://cveledger.app/badge/CVE-2025-40171.svg)](https://cveledger.app/cve/CVE-2025-40171)

Record last updated .