CVE-2026-89968

published 16 Sep 2026 · updated 15 Nov 2026

nvmet-tcp: reject unsolicited H2CData PDUs

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel db62b35cbca052860c519cbcabe7650708528738, Kernel 02341ee424fb2eed16b5b8a9d247492e49335c21, Kernel 14beef7d4f123fb458fc9844aa74a071871dcca6 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <db62b35cbca052860c519cbcabe7650708528738, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <02341ee424fb2eed16b5b8a9d247492e49335c21, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <14beef7d4f123fb458fc9844aa74a071871dcca6, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <1cbed7538946c99e585acefd11c9ba3a0bdbae05, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <2b71f9193e3d3a352920ba367f1a6db345249038, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <9fb527103e53fd43a8e802c2eca407869c204f7a, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <cade124c06f8e738e3a0df285ed2e08953e6bfaa, >=872d26a391da92ed8f0c0f5cb5fef428067b7f30 <cf1484d9a75de6809ef331e16f525aaa41b0e16d, =5.0db62b35cbca052860c519cbcabe7650708528738, 02341ee424fb2eed16b5b8a9d247492e49335c21, 14beef7d4f123fb458fc9844aa74a071871dcca6, 1cbed7538946c99e585acefd11c9ba3a0bdbae05, 2b71f9193e3d3a352920ba367f1a6db345249038, 9fb527103e53fd43a8e802c2eca407869c204f7a, cade124c06f8e738e3a0df285ed2e08953e6bfaa, cf1484d9a75de6809ef331e16f525aaa41b0e16d
linux-kernel: Kernel>=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=5.0.0 <5.10.2705.15.221, 6.1.188, 6.18.51, 7.2.5, 6.6.157, 6.12.110, 5.10.270

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89968 severity on Zeptric[![CVE-2026-89968](https://zeptric.io/badge/cve/CVE-2026-89968.svg)](https://zeptric.io/cve/CVE-2026-89968)