Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-92525, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Received3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 69d3ccf6543f24c452a020c8028ca6f46cb1e8db
    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 750bba6ce9bb0b11d6a166031c9728ae3f21765e
    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < c067aa7b231e91a18a1b3666201ab14dfb00347a
    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 13cb7160e5b791f5e3ecf9311cf32849fe7e9b62
    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 5ec111ddc1f727c1e4580aea459842ae5a8359a5
    • affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 126c757e4cd46f866ddc283143b58eb4d9bf52cd
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-92525 badge
[![CVE-2026-92525](https://cveledger.app/badge/CVE-2026-92525.svg)](https://cveledger.app/cve/CVE-2026-92525)

Record last updated .