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-2026-46135nvmet-tcp: fix race between ICReq handling and queue teardown

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix race between ICReq handling and queue teardown nvmet_tcp_handle_icreq() updates queue->state after sending an Initialization Connection Response (ICResp), but it does so without serializing against target-side queue teardown. If an NVMe/TCP host sends an Initialization Connection Request (ICReq) and immediately closes the connection, target-side teardown may start in softirq context before io_work drains the already buffered ICReq. In that case, nvmet_tcp_schedule_release_queue() sets queue->state to NVMET_TCP_Q_DISCONNECTING and drops the queue reference under state_lock. If io_work later processes that ICReq, nvmet_tcp_handle_icreq() can still overwrite the state back to NVMET_TCP_Q_LIVE. That defeats the DISCONNECTING-state guard in nvmet_tcp_schedule_release_queue() and allows a later socket state change to re-enter teardown and issue a second kref_put() on an already released queue. The ICResp send failure path has the same problem. If teardown has already moved the queue to DISCONNECTING, a send error can still overwrite the state with NVMET_TCP_Q_FAILED, again reopening the window for a second teardown path to drop the queue reference. Fix this by serializing both post-send state transitions with state_lock and bailing out if teardown has already started. Use -ESHUTDOWN as an internal sentinel for that bail-out path rather than propagating it as a transport error like -ECONNRESET. Keep nvmet_tcp_socket_error() setting rcv_state to NVMET_TCP_RECV_ERR before honoring that sentinel so receive-side parsing stays quiesced until the existing release path completes.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-2026-46135, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Undergoing Analysis3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 66% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < b7dd4d27aa70bd98bb10572310e913668baf6a65
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 9c63cf80895a70eb4fcfcaa725bb1ac9ae76f02b
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 6f96dea4819d122737b217ea16660d255abbf8c6
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 5f0b95ef68ab9afba75b20eebf436130f80c161a
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < dcfe4d1f7960e7d1c01642318f3aae1a604f8508
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 5293a8882c549fab4a878bc76b0b6c951f980a61
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.88 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .