{"id":24660,"date":"2026-09-16T20:32:36","date_gmt":"2026-09-16T12:32:36","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89973"},"modified":"2026-09-16T20:32:36","modified_gmt":"2026-09-16T12:32:36","slug":"cve-2026-89973","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89973","title":{"rendered":"CVE-2026-89973 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: check the d"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvme-tcp: check the data direction of a C2HData PDU<\/p>\n<p>nvme_tcp_handle_c2h_data() finds the request by command id and checks<br \/>\nthat it has a payload, but it does not check that the command asked for<br \/>\ndata to be read.  A controller that answers a write command with C2HData<br \/>\ntherefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits<br \/>\nWARN_ON_ONCE(i-&gt;data_source) and returns 0.  The receive path turns that<br \/>\ninto -EFAULT and resets the controller.<\/p>\n<p>No data is copied, so this is not memory corruption.  What a controller<br \/>\ngets is a kernel warning it can raise at will, which is fatal on a host<br \/>\nbooted with panic_on_warn.<\/p>\n<p>The send path already knows the direction &#8211; it consults rq_data_dir()<br \/>\nwhen it builds a command &#8211; and nvme_tcp_handle_r2t() checks the length<br \/>\nand the offset of the request it names.  The C2HData path does not check<br \/>\nthe direction at all.<\/p>\n<p>Reject a C2HData PDU whose command is not a read.  Rejecting it fails<br \/>\nthe command and resets the controller, as the neighbouring check in this<br \/>\nfunction does; what goes away is the warning.<\/p>\n<p>  [    6.885580] &#8212;&#8212;&#8212;&#8212;[ cut here ]&#8212;&#8212;&#8212;&#8212;<br \/>\n  [    6.886457] WARNING: lib\/iov_iter.c:193 at _copy_to_iter+0x289\/0x1330, CPU#0: kworker\/0:1H\/71<br \/>\n  [    6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker\/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy)<br \/>\n  [    6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work<br \/>\n  [    6.891875] RIP: 0010:_copy_to_iter+0x289\/0x1330<br \/>\n  [    6.903739] Call Trace:<br \/>\n  [    6.904085]<br \/>\n  [    6.909254]  __skb_datagram_iter+0x433\/0x820<br \/>\n  [    6.911026]  skb_copy_datagram_iter+0x37\/0x120<br \/>\n  [    6.911622]  nvme_tcp_recv_skb+0xa07\/0x4320<br \/>\n  [    6.913378]  __tcp_read_sock+0x1ab\/0x810<br \/>\n  [    6.915788]  nvme_tcp_try_recv+0x152\/0x1e0<br \/>\n  [    6.918222]  nvme_tcp_io_work+0x1e4\/0x6c0<br \/>\n  [    6.926906]<br \/>\n  [    6.927226] &#8212;[ end trace 0000000000000000 ]&#8212;<br \/>\n  [    6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data<br \/>\n  [    6.928709] nvme nvme0: receive failed:  -14<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvme-tcp: check the data direction of a C2HData PDU<\/p>\n<p>nvme_tcp_handle_c2h_data() finds the request by command id and checks<br \/>\nthat it <\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-24660","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/24660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=24660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=24660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=24660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}