Към съдържанието

CVE-2026-46135: Linux, състезание за ресурс

9.8

CVSS 3.1

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

Атакува се по мрежата, без особени условия, без вход и без действие от потребителя.

CVE радар: още уязвимости от този вид

  • Експлоатация: няма данни за експлоатация
  • Атаката може да се автоматизира

Описание

Оригинално описание

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.

Засегнати продукти

  • Linux Linux: 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди b7dd4d27aa70bd98bb10572310e913668baf6a65; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 9c63cf80895a70eb4fcfcaa725bb1ac9ae76f02b; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 6f96dea4819d122737b217ea16660d255abbf8c6; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 5f0b95ef68ab9afba75b20eebf436130f80c161a; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 49891c8fe0cb43fbbe480da1cdccfbbaeb820cb3; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 67e1aaf93b495c2f10bc8a5fbba575fbb7f449b6; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди dcfe4d1f7960e7d1c01642318f3aae1a604f8508; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 преди 5293a8882c549fab4a878bc76b0b6c951f980a61
  • Linux Linux: 5.0; преди 5.0; 5.10.261 до 5.10.*; 5.15.212 до 5.15.*; 6.1.178 до 6.1.*; 6.6.144 до 6.6.*; 6.12.88 до 6.12.*; 6.18.30 до 6.18.*; 7.0.7 до 7.0.*; 7.1 до *

Вид слабост

История

  • 28 май 2026 Публикувано

Други уязвимости в Linux Linux

Първоизточници

CVE-2026-46135: Linux, състезание за ресурс | freedomonline.bg