CVE-2026-46135

Advisory lineage Upstream: 0 Downstream: 18
Awaiting Analysis
Published: 28 May 2026, 09:35
Last modified:04 Jul 2026, 11:50

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.8 CRITICAL
v3.1 (cve.org)
EPSS Score
0.35% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

28 May 2026, 09:35
Published
Vulnerability first disclosed
04 Jul 2026, 11:50
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•CRITICAL•Score: 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.35%• Percentile: 27%

Affected Systems

  • linux•linux

    ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < dcfe4d1f7960e7d1c01642318f3aae1a604f8508 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 5293a8882c549fab4a878bc76b0b6c951f980a61 | < 6.12.88 | < 6.18.30 | < 7.0.7 | ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 5f0b95ef68ab9afba75b20eebf436130f80c161a | ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3 | ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6 | ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < dcfe4d1f7960e7d1c01642318f3aae1a604f8508 | ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 5293a8882c549fab4a878bc76b0b6c951f980a61 | 5.0

References (5)