{"id":26008,"date":"2026-09-18T04:32:13","date_gmt":"2026-09-17T20:32:13","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-93151"},"modified":"2026-09-18T04:32:13","modified_gmt":"2026-09-17T20:32:13","slug":"cve-2026-93151","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-93151","title":{"rendered":"CVE-2026-93151 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-rdma: fix respo"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvmet-rdma: fix response resource leak on queue teardown<\/p>\n<p>When an nvme target with rdma transport is removed while I\/Os are in<br \/>\nflight, a response can be posted but its send completion is never<br \/>\ndelivered before the connection is torn down. As a result<br \/>\nnvmet_rdma_send_done() and nvmet_rdma_release_rsp() are never called for<br \/>\nthe response, and this leaks the allocated RDMA read\/write context and<br \/>\nrequest SGLs.<\/p>\n<p>These leaks are recreated by running blktests nvme\/061 with the rdma<br \/>\ntransport and the siw driver. Kernel kmemleak feature reports them as<br \/>\nfollows:<\/p>\n<p>  unreferenced object 0xffff88812bc490c0 (size 32):<br \/>\n    comm &#8220;kworker\/2:1H&#8221;, pid 409, jiffies 4307744490<br \/>\n    backtrace (crc 89afd339):<br \/>\n      __kmalloc_noprof+0x5f9\/0x890<br \/>\n      sgl_alloc_order+0x7b\/0x380<br \/>\n      nvmet_req_alloc_sgls+0x290\/0x4f0 [nvmet]<br \/>\n      nvmet_rdma_map_sgl_keyed+0x241\/0x12e0 [nvmet_rdma]<br \/>\n      nvmet_rdma_handle_command+0x73e\/0xb80 [nvmet_rdma]<br \/>\n      __ib_process_cq+0x149\/0x4c0 [ib_core]<br \/>\n      ib_cq_poll_work+0x49\/0x160 [ib_core]<br \/>\n      process_one_work+0x8b2\/0x1640<br \/>\n      worker_thread+0x5fd\/0xfe0<br \/>\n      kthread+0x367\/0x460<br \/>\n      ret_from_fork+0x655\/0x9d0<br \/>\n      ret_from_fork_asm+0x1a\/0x30<\/p>\n<p>  unreferenced object 0xffff88814bd05e80 (size 64):<br \/>\n    comm &#8220;kworker\/3:1H&#8221;, pid 148, jiffies 4295195428<br \/>\n    backtrace (crc e35510cb):<br \/>\n      __kmalloc_noprof+0x5f9\/0x890<br \/>\n      rdma_rw_ctx_init+0x333\/0x1fa0 [ib_core]<br \/>\n      nvmet_rdma_map_sgl_keyed+0x5c8\/0x12e0 [nvmet_rdma]<br \/>\n      nvmet_rdma_handle_command+0x73e\/0xb80 [nvmet_rdma]<br \/>\n      __ib_process_cq+0x149\/0x4c0 [ib_core]<br \/>\n      ib_cq_poll_work+0x49\/0x160 [ib_core]<br \/>\n      process_one_work+0x8b2\/0x1640<br \/>\n      worker_thread+0x5fd\/0xfe0<br \/>\n      kthread+0x367\/0x460<br \/>\n      ret_from_fork+0x655\/0x9d0<br \/>\n      ret_from_fork_asm+0x1a\/0x30<\/p>\n<p>To avoid the memory leaks, reclaim the memory of the in-flight responses<br \/>\nwhen the queue QP is torn down. Call nvmet_rdma_free_rsp_resources()<br \/>\nthat frees up the RDMA read\/write context and the request SGLs of such<br \/>\nresponses.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvmet-rdma: fix response resource leak on queue teardown<\/p>\n<p>When an nvme target with rdma transport is removed while I\/Os are in<br \/>\nflig<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-26008","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/26008","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=26008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=26008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=26008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}