CVE-2026-52989
nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
24 Jun 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
Currently, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds
PDU length or offset, it triggers nvmet_tcp_fatal_error(cmd->queue)
and returns early. However, because the function returns void, the
callers are entirely unaware that a fatal error has occurred and
that the cmd->recv_msg.msg_iter was left uninitialized.
Callers such as nvmet_tcp_handle_h2c_data_pdu() proceed to blindly
overwrite the queue state with queue->rcv_state = NVMET_TCP_RECV_DATA
Consequently, the socket receiving loop may attempt to read incoming
network data into the uninitialized iterator.
Fix this by shifting the error handling responsibility to the callers.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/046fa5c72d15cd8e2d592e275697ea399d8f76b0https://git.kernel.org/stable/c/3df42a854686fa06484e37ac1a3931c8e3e3453chttps://git.kernel.org/stable/c/c2a11441538bdbbc5aa003f190995eba93a89b88https://git.kernel.org/stable/c/d7c8f95f599b3b38a717d2e771c3f8c174f657c3https://git.kernel.org/stable/c/ea8e356acb165cb1fd75537a52e1f66e5e76c538https://git.kernel.org/stable/c/f9204a2b78dd18374d3bcf9bf93d9021ce22de1b