Menu

Star on GitHub · 3.4k

CVE-2026-92525

7.1 · HIGH

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…

Published Sep 17, 2026EPSS 0.16%

Overview

CVE-2026-92525 is a high-severity vulnerability. It was published on September 17, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 d

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-92525?

CVE-2026-92525 is a high-severity vulnerability. It was published on September 17, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2026-92525?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-92525?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-92525?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-92525 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Watch the demo →