CVE-2026-93151
CVE CVE-2026-93151EUVD EUVD-2026-82259Published 2026-09-17T16:11:47.000ZLast changed 2026-09-18T17:56:15.000ZCVSS 7.5
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: fix response resource leak on queue teardown When an nvme target with rdma transport is removed while I/Os are in flight, a response can be posted but its send completion is never delivered before the connection is torn down. As a result nvmet_rdma_send_done() and nvmet_rdma_release_rsp() are never called for the response, and this leaks the allocated RDMA read/write context and request SGLs. These leaks are recreated by running blktests nvme/061 with the rdma transport and the siw driver. Kernel kmemleak feature reports them as follows: unreferenced object 0xffff88812bc490c0 (size 32): comm "kworker/2:1H", pid 409, jiffies 4307744490 backtrace (crc 89afd339): __kmalloc_noprof+0x5f9/0x890 sgl_alloc_order+0x7b/0x380 nvmet_req_alloc_sgls+0x290/0x4f0 [nvmet] nvmet_rdma_map_sgl_keyed+0x241/0x12e0 [nvmet_rdma] nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma] __ib_process_cq+0x149/0x4c0 [ib_core] ib_cq_poll_work+0x49/0x160 [ib_core] process_one_work+0x8b2/0x1640 worker_thread+0x5fd/0xfe0 kthread+0x367/0x460 ret_from_fork+0x655/0x9d0 ret_from_fork_asm+0x1a/0x30 unreferenced object 0xffff88814bd05e80 (size 64): comm "kworker/3:1H", pid 148, jiffies 4295195428 backtrace (crc e35510cb): __kmalloc_noprof+0x5f9/0x890 rdma_rw_ctx_init+0x333/0x1fa0 [ib_core] nvmet_rdma_map_sgl_keyed+0x5c8/0x12e0 [nvmet_rdma] nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma] __ib_process_cq+0x149/0x4c0 [ib_core] ib_cq_poll_work+0x49/0x160 [ib_core] process_one_work+0x8b2/0x1640 worker_thread+0x5fd/0xfe0 kthread+0x367/0x460 ret_from_fork+0x655/0x9d0 ret_from_fork_asm+0x1a/0x30 To avoid the memory leaks, reclaim the memory of the in-flight responses when the queue QP is torn down. Call nvmet_rdma_free_rsp_resources() that frees up the RDMA read/write context and the request SGLs of such responses.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <9584b3c30e4ee8ca315bdc12249cc6c47cf1a482; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <91cfa74f1f3772e8c3662c064a45d8633e00c78e; patch: 7.3-rc1; patch: 6.12.110; patch: 6.6.157; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c; 4.8; patch: 6.18.52; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50; patch: 7.2.6; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <0114dd303b373522dea06053aabae34bdd33a7c4; patch: 5.15.221; 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b <5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08; patch: 0; patch: 6.1.188
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.