CVE-2026-89968nvmet-tcp: reject unsolicited H2CData PDUs
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: reject unsolicited H2CData PDUs nvmet_tcp_handle_h2c_data_pdu() accepts an H2CData PDU after only checking that its TTAG is a valid in-range command index and that the command's data buffers are mapped. It never checks that the target has actually solicited that data by sending an R2T for the command. A remote host can abuse this. It submits a write command that takes the R2T path and, before the target transmits the R2T, sends an H2CData PDU for that command's tag. The data completes the command early, and when the command then fails synchronously (e.g. a length mismatch caught by nvmet_check_transfer_len()), it is completed a second time. Each completion calls nvmet_tcp_queue_response(), so the same command is added to queue->resp_list twice while it is still linked; the second llist_add() makes the node point to itself (lentry->next == lentry). nvmet_tcp_process_resp_list() then walks that self-referential node and adds the command to resp_send_list twice. With CONFIG_DEBUG_LIST this trips the "list_add double add" check (kernel BUG); without it the loop never terminates and the nvmet_tcp workqueue wedges (soft-lockup). It is remotely triggerable and needs no authentication on an allow_any_host subsystem. Track whether an R2T has been transmitted for a command and reject an H2CData PDU that arrives before it. The flag is cleared on command reuse (nvmet_tcp_get_cmd() zeroes cmd->flags) and stays set across the multiple H2CData PDUs of a single solicited transfer.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 872d26a391da92ed8f0c0f5cb5fef428067b7f30 before 02341ee424fb2eed16b5b8a9d247492e49335c21; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30 before cade124c06f8e738e3a0df285ed2e08953e6bfaa; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 builds before 14beef7d4f123fb458fc9844aa74a071871dcca6; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 builds before 9fb527103e53fd43a8e802c2eca407869c204f7a; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 builds before 2b71f9193e3d3a352920ba367f1a6db345249038; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30 before cf1484d9a75de6809ef331e16f525aaa41b0e16d; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 builds before 1cbed7538946c99e585acefd11c9ba3a0bdbae05; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30 before db62b35cbca052860c519cbcabe7650708528738 | CNA record |
References
- https://git.kernel.org/stable/c/02341ee424fb2eed16b5b8a9d247492e49335c21
- https://git.kernel.org/stable/c/cade124c06f8e738e3a0df285ed2e08953e6bfaa
- https://git.kernel.org/stable/c/14beef7d4f123fb458fc9844aa74a071871dcca6
- https://git.kernel.org/stable/c/9fb527103e53fd43a8e802c2eca407869c204f7a
- https://git.kernel.org/stable/c/2b71f9193e3d3a352920ba367f1a6db345249038
- https://git.kernel.org/stable/c/cf1484d9a75de6809ef331e16f525aaa41b0e16d
- https://git.kernel.org/stable/c/1cbed7538946c99e585acefd11c9ba3a0bdbae05
- https://git.kernel.org/stable/c/db62b35cbca052860c519cbcabe7650708528738
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.