CVE-2026-46135

Aliases:UBUNTU-CVE-2026-46135DEBIAN-CVE-2026-46135
Advisory lineage Upstream: 0 Downstream: 30
Undergoing Analysis
Published: 28 May 2026, 09:35
Last modified:05 Aug 2026, 12:29

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.8 CRITICAL
v3.1 (cve.org)
EPSS Score
0.4% 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
05 Aug 2026, 12:29
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

  • v4.0•CRITICAL•Score: 9.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • 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.40%• Percentile: 34%

Techniques & Countermeasures

  • CWE-362•Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

    The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Systems

  • debian•linux

    < 5.10.262-1 | < 6.1.180-1 | < 6.12.88-1 | < 7.0.7-1

  • debian•linux-6.1

    < 6.1.180-1~deb11u1

  • ubuntu•linux

    < 5.4.0-233.253 | < 5.15.0-185.195 | < 6.8.0-134.134 | < 6.17.0-40.40 | < 7.0.0-27.27

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    < 5.4.0-1161.172 | < 5.15.0-1111.118 | < 6.8.0-1060.63 | < 6.17.0-1019.19 | < 7.0.0-1008.8

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.15

    < 5.15.0-1111.118~20.04.1

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.4

    < 5.4.0-1161.172~18.04.1

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.14

    all

  • ubuntu•linux-aws-6.17

    < 6.17.0-1019.19~24.04.1

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-6.5

    all

  • ubuntu•linux-aws-6.8

    < 6.8.0-1060.63~22.04.1

  • ubuntu•linux-aws-fips

    < 5.4.0-1161.172+fips1 | all | < 5.15.0-1111.118+fips1 | < 6.8.0-1060.63+fips1

  • ubuntu•linux-azure

    all | < 5.4.0-1166.172 | < 5.15.0-1116.125 | < 6.8.0-1063.71 | all | < 7.0.0-1010.10

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.15

    < 5.15.0-1116.125~20.04.1

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.4

    < 5.4.0-1166.172~18.04.1

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.11

    all

  • ubuntu•linux-azure-6.14

    all

  • ubuntu•linux-azure-6.17

    < 6.17.0-1021.21~24.04.1

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-6.5

    all

  • ubuntu•linux-azure-6.8

    < 6.8.0-1063.71~22.04.1

  • ubuntu•linux-azure-7.0

    all

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all | all | < 6.8.0-1062.69 | all | < 7.0.0-1009.9

  • ubuntu•linux-azure-fde-5.15

    < 5.15.0-1116.125~20.04.1

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.14

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fde-6.8

    < 6.8.0-1062.69~22.04.1

  • ubuntu•linux-azure-fips

    < 5.4.0-1166.172+fips1 | all | < 5.15.0-1116.125+fips1 | < 6.8.0-1062.69+fips1

  • ubuntu•linux-azure-nvidia

    all

  • ubuntu•linux-azure-nvidia-6.14

    all

  • ubuntu•linux-bluefield

    all | < 5.4.0-1120.127 | < 5.15.0-1095.97 | < 6.8.0-1026.30

  • ubuntu•linux-fips

    < 5.4.0-1135.145 | all | < 5.15.0-185.195+fips1 | < 6.8.0-134.134+fips1

  • ubuntu•linux-gcp

    all | < 5.4.0-1164.173 | < 5.15.0-1111.121 | < 6.8.0-1063.69 | < 6.17.0-1020.22 | < 7.0.0-1007.7

  • ubuntu•linux-gcp-5.11

    all

  • ubuntu•linux-gcp-5.13

    all

  • ubuntu•linux-gcp-5.15

    < 5.15.0-1111.121~20.04.1

Showing first 50 affected entries in server-rendered view.

References (49)