{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-93151", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-93151" ], "published": "2026-09-17T16:10:40Z", "summary": "nvmet-rdma: fix response resource leak on queue teardown", "details": "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.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.47-1+rpt4" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" } ] }, "database_specific": { "per_version": { "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.188", "compiled_filter": false } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-93151" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/91cfa74f1f3772e8c3662c064a45d8633e00c78e" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/9584b3c30e4ee8ca315bdc12249cc6c47cf1a482" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/0114dd303b373522dea06053aabae34bdd33a7c4" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-09-18T17:55:42Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.5, "cvss_v3_severity": "High", "scenario": "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." } } }