{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-93151","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-17T16:02:15.089Z","datePublished":"2026-09-17T16:11:47.559Z","dateUpdated":"2026-09-18T17:56:15.483Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-09-18T17:56:15.483Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-rdma: fix response resource leak on queue teardown\n\nWhen an nvme target with rdma transport is removed while I/Os are in\nflight, a response can be posted but its send completion is never\ndelivered before the connection is torn down. As a result\nnvmet_rdma_send_done() and nvmet_rdma_release_rsp() are never called for\nthe response, and this leaks the allocated RDMA read/write context and\nrequest SGLs.\n\nThese leaks are recreated by running blktests nvme/061 with the rdma\ntransport and the siw driver. Kernel kmemleak feature reports them as\nfollows:\n\n  unreferenced object 0xffff88812bc490c0 (size 32):\n    comm \"kworker/2:1H\", pid 409, jiffies 4307744490\n    backtrace (crc 89afd339):\n      __kmalloc_noprof+0x5f9/0x890\n      sgl_alloc_order+0x7b/0x380\n      nvmet_req_alloc_sgls+0x290/0x4f0 [nvmet]\n      nvmet_rdma_map_sgl_keyed+0x241/0x12e0 [nvmet_rdma]\n      nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma]\n      __ib_process_cq+0x149/0x4c0 [ib_core]\n      ib_cq_poll_work+0x49/0x160 [ib_core]\n      process_one_work+0x8b2/0x1640\n      worker_thread+0x5fd/0xfe0\n      kthread+0x367/0x460\n      ret_from_fork+0x655/0x9d0\n      ret_from_fork_asm+0x1a/0x30\n\n  unreferenced object 0xffff88814bd05e80 (size 64):\n    comm \"kworker/3:1H\", pid 148, jiffies 4295195428\n    backtrace (crc e35510cb):\n      __kmalloc_noprof+0x5f9/0x890\n      rdma_rw_ctx_init+0x333/0x1fa0 [ib_core]\n      nvmet_rdma_map_sgl_keyed+0x5c8/0x12e0 [nvmet_rdma]\n      nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma]\n      __ib_process_cq+0x149/0x4c0 [ib_core]\n      ib_cq_poll_work+0x49/0x160 [ib_core]\n      process_one_work+0x8b2/0x1640\n      worker_thread+0x5fd/0xfe0\n      kthread+0x367/0x460\n      ret_from_fork+0x655/0x9d0\n      ret_from_fork_asm+0x1a/0x30\n\nTo avoid the memory leaks, reclaim the memory of the in-flight responses\nwhen the queue QP is torn down. Call nvmet_rdma_free_rsp_resources()\nthat frees up the RDMA read/write context and the request SGLs of such\nresponses."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - A remote initiator's NVMe capsule with a keyed SGL (NVME_KEY_SGL_FMT_DATA_DESC) is delivered by RDMA RECV into nvmet_rdma_recv_done, which calls nvmet_rdma_map_sgl_keyed; the same peer then raises RDMA_CM_EVENT_DISCONNECTED in nvmet_rdma_cm_handler. nvmet_rdma_enable_port listens with RDMA_PS_TCP on NVME_RDMA_IP_PORT (4420) over RoCEv2/iWARP, which are IP-routable.\nAC:L - The initiator controls both halves: it sends keyed-SGL commands so nvmet_rdma_map_sgl_keyed allocates the SGL and rdma_rw_ctx, then closes the QP so nvmet_rdma_destroy_queue_ib runs while rsp_tags bits remain set because nvmet_rdma_send_done never ran. blktests nvme/061 reproduces this; no uninfluenced race or layout is required.\nPR:N - nvmet_rdma_queue_connect accepts the RDMA CM CONNECT_REQUEST with no authentication. I/O that reaches nvmet_rdma_map_sgl_keyed only needs nvmet_req_init to succeed; nvmet_check_auth_status is true unless a DH-HMAC-CHAP host_key is configured, and nvmet_host_allowed admits a client-supplied host NQN or allow_any_host.\nUI:N - The attacker submits the keyed-SGL capsule and disconnects its own RDMA connection; nvmet_rdma_cm_handler delivers RDMA_CM_EVENT_DISCONNECTED into nvmet_rdma_queue_disconnect with no local user or administrator action.\nS:U - The leaked sgl_alloc pages and rdma_rw_ctx sit in the nvmet-rdma target kernel's allocator; the bug does not cross a VM, IOMMU, or other security-authority boundary.\nC:N - nvmet_rdma_destroy_queue_ib frees the QP without calling nvmet_rdma_free_rsp_resources, so the SGL pages and rdma_rw_ctx are orphaned. Those objects are never copied back to the initiator or otherwise disclosed.\nI:N - The orphaned scatterlist from nvmet_req_alloc_sgls and the rdma_rw_ctx from rdma_rw_ctx_init are leaked, not reused, so there is no write primitive, use-after-free, or kernel-state corruption.\nA:H - Each in-flight keyed-SGL command leaks the pages sgl_alloc obtained (up to 2^NVMET_RDMA_MAX_MDTS * 4KB, 1MB) plus the rdma_rw_ctx. Repeating RDMA connect, queue-depth READs, and RDMA_CM_EVENT_DISCONNECTED exhausts kernel memory and can OOM the target."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/target/rdma.c"],"versions":[{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"91cfa74f1f3772e8c3662c064a45d8633e00c78e","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"9584b3c30e4ee8ca315bdc12249cc6c47cf1a482","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50","status":"affected","versionType":"git"},{"version":"8f000cac6e7a6edca7ab93bafc7ed28b27c1545b","lessThan":"0114dd303b373522dea06053aabae34bdd33a7c4","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/target/rdma.c"],"versions":[{"version":"4.8","status":"affected"},{"version":"0","lessThan":"4.8","status":"unaffected","versionType":"semver"},{"version":"5.15.221","lessThanOrEqual":"5.15.*","status":"unaffected","versionType":"semver"},{"version":"6.1.188","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.6.157","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.110","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.52","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.2.6","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"5.15.221"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"6.1.188"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"6.6.157"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"6.12.110"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"6.18.52"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"7.2.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8","versionEndExcluding":"7.3-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/91cfa74f1f3772e8c3662c064a45d8633e00c78e"},{"url":"https://git.kernel.org/stable/c/156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7"},{"url":"https://git.kernel.org/stable/c/9584b3c30e4ee8ca315bdc12249cc6c47cf1a482"},{"url":"https://git.kernel.org/stable/c/5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08"},{"url":"https://git.kernel.org/stable/c/ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c"},{"url":"https://git.kernel.org/stable/c/d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50"},{"url":"https://git.kernel.org/stable/c/0114dd303b373522dea06053aabae34bdd33a7c4"}],"title":"nvmet-rdma: fix response resource leak on queue teardown","x_generator":{"engine":"bippy-1.2.0"}}}}