Shellfeed logo Shellfeed

CVE-2026-92525 · HIGH (CVSS 7.1)

Summary: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[]

EPSS: 0.2% probability of exploitation in the next 30 days (percentile 5.7).

Details

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.

Severity

HIGH (CVSS 7.1) — vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Affected packages

  • GIT git.kernel.org/pub/scm/linux/kernel/git/stable/linux [8700e3e7c4857d28ebaa824509934556da0b3e76 – 69d3ccf6543f24c452a020c8028ca6f46cb1e8db]
  • Linux Kernel [4.8.0 – 6.1.188] [6.2.0 – 6.6.157] [6.7.0 – 6.12.110] [6.13.0 – 6.18.52] [6.19.0 – 7.2.6]

References