Description
In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp

rxe_qp_from_attr() handles IB_QP_MAX_DEST_RD_ATOMIC outside the
IB_QP_STATE path, so it holds no state_lock and runs while the responder
task rxe_receiver() (recv_task on rxe_wq) is live. A modify_qp() setting
only that attribute calls free_rd_atomic_resources() then
alloc_rd_atomic_resources(), swapping qp->resp.resources[] while
rxe_prepare_res()/find_resource() walk it; free_rd_atomic_resources()
also leaves the cached pointer qp->resp.res dangling. A local
unprivileged user can race the free/realloc into a use-after-free in
rxe_receiver() (local DoS).

Drain recv_task around the swap with rxe_disable_task()/rxe_enable_task(),
as rxe_qp_reset() already does when tearing this array down, re-enabling
only after alloc_rd_atomic_resources() succeeds so the responder never
resumes against a NULL qp->resp.resources on the ENOMEM path. Also clear
qp->resp.res in free_rd_atomic_resources(), like the rxe_resp.c
completion paths.

Reproduced under KASAN; the slab-use-after-free in rxe_receiver() is gone.
Published: 2026-09-04
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Apply Patch
AI Analysis

Impact

The vulnerability originates in the Linux kernel's RDMA/rxe subsystem, specifically during the modification of the IB_QP_MAX_DEST_RD_ATOMIC attribute. The kernel code lacks proper locking when reallocating resources, allowing a local unprivileged user to race a free and allocate sequence. This race condition results in a use‑after‑free within the rxe_receiver() task, causing the system to crash or become unresponsive. The primary impact is a local denial of service rather than remote code execution or data exfiltration. The weakness is a classic use‑after‑free flaw that can be easily triggered by an attacker who can execute code on the affected machine.

Affected Systems

This issue affects the Linux kernel, as the CVE references kernel commit logs and the designated CPE is cpe:2.3:o:linux:linux_kernel. No specific kernel version range is listed in the entry, so any installation of the Linux kernel that contains the vulnerable rxe driver code is potentially affected. System administrators should verify whether their kernel build includes rxe support and whether the patch has been applied.

Risk and Exploitability

The exploit requires local privileges and a race condition, meaning the attack is relatively straightforward for any user who can run commands on the machine. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Without an assigned CVSS score, the exact severity cannot be quantified from the available data, but the local denial of service nature indicates a moderate to high risk for systems that rely on RDMA functionality. Organizations that disable RDMA or patch the kernel will mitigate this risk.

Generated by OpenCVE AI on September 4, 2026 at 19:13 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a revision that includes the rxe_qp_from_attr fix, such as the commit referenced in the advisory.
  • If an immediate kernel update is not possible, consider disabling the RDMA/rxe subsystem using module unload or kernel command line options until a patch can be applied.
  • For systems where RDMA is critical, apply a backport of the upstream fix to the current kernel version.

Generated by OpenCVE AI on September 4, 2026 at 19:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 19:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Fri, 04 Sep 2026 16:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp rxe_qp_from_attr() handles IB_QP_MAX_DEST_RD_ATOMIC outside the IB_QP_STATE path, so it holds no state_lock and runs while the responder task rxe_receiver() (recv_task on rxe_wq) is live. A modify_qp() setting only that attribute calls free_rd_atomic_resources() then alloc_rd_atomic_resources(), swapping qp->resp.resources[] while rxe_prepare_res()/find_resource() walk it; free_rd_atomic_resources() also leaves the cached pointer qp->resp.res dangling. A local unprivileged user can race the free/realloc into a use-after-free in rxe_receiver() (local DoS). Drain recv_task around the swap with rxe_disable_task()/rxe_enable_task(), as rxe_qp_reset() already does when tearing this array down, re-enabling only after alloc_rd_atomic_resources() succeeds so the responder never resumes against a NULL qp->resp.resources on the ENOMEM path. Also clear qp->resp.res in free_rd_atomic_resources(), like the rxe_resp.c completion paths. Reproduced under KASAN; the slab-use-after-free in rxe_receiver() is gone.
Title RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-04T15:55:18.791Z

Reserved: 2026-08-26T14:34:25.798Z

Link: CVE-2026-80864

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T16:18:15.737

Modified: 2026-09-04T16:18:15.737

Link: CVE-2026-80864

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-05T02:15:06Z

Weaknesses