---
id: CVE-2026-92525
title: |-
  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 i…
summary: |-
  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 i…
severity: high
cvss: 7.1
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    69d3ccf6543f24c452a020c8028ca6f46cb1e8db
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    750bba6ce9bb0b11d6a166031c9728ae3f21765e
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    c067aa7b231e91a18a1b3666201ab14dfb00347a
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    13cb7160e5b791f5e3ecf9311cf32849fe7e9b62
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    5ec111ddc1f727c1e4580aea459842ae5a8359a5
  - >-
    Linux >= 8700e3e7c4857d28ebaa824509934556da0b3e76 <
    126c757e4cd46f866ddc283143b58eb4d9bf52cd
  - Linux 4.8
published: '2026-09-17'
updated: '2026-09-18'
sourceUpdated: '2026-09-18T18:18:14.300'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92525'
references:
  - url: 'https://git.kernel.org/stable/c/126c757e4cd46f866ddc283143b58eb4d9bf52cd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/13cb7160e5b791f5e3ecf9311cf32849fe7e9b62'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5ec111ddc1f727c1e4580aea459842ae5a8359a5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/69d3ccf6543f24c452a020c8028ca6f46cb1e8db'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/750bba6ce9bb0b11d6a166031c9728ae3f21765e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c067aa7b231e91a18a1b3666201ab14dfb00347a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.00167
epssPercentile: 0.05211
ingestedAt: '2026-09-17T16:21:47.774Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.