CVE-2026-80864RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 56 days later
· 56 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 91% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 87e40635d77aa19088550698c81eb295d5131f71
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 82257379061c0a7aba6c77081d988339982af115
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 0136b528b753c5a56e4d997ef20b86bb6750b8fb
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < ffa4f0be69656be1755090f02db38d49816585c6
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < d4cd32eb8bd2b0ffbdc7b1f3d82ce6a371f8f844
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 60dfd47929cd1e7070daa810d40ce538d888410d
- affected 8700e3e7c4857d28ebaa824509934556da0b3e76 – < 6f7014237405e7f032b5c53a82d9eccf6161c291
- affected 4.8
- unaffected < 4.8
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.108 – ≤ 6.12.*
- unaffected 6.18.49 – ≤ 6.18.*
- unaffected 7.1.13 – ≤ 7.1.*
- unaffected 7.2.3 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/87e40635d77aa19088550698c81eb295d5131f71 (opens in a new tab)
- https://git.kernel.org/stable/c/82257379061c0a7aba6c77081d988339982af115 (opens in a new tab)
- https://git.kernel.org/stable/c/0136b528b753c5a56e4d997ef20b86bb6750b8fb (opens in a new tab)
- https://git.kernel.org/stable/c/ffa4f0be69656be1755090f02db38d49816585c6 (opens in a new tab)
- https://git.kernel.org/stable/c/d4cd32eb8bd2b0ffbdc7b1f3d82ce6a371f8f844 (opens in a new tab)
- https://git.kernel.org/stable/c/60dfd47929cd1e7070daa810d40ce538d888410d (opens in a new tab)
- https://git.kernel.org/stable/c/6f7014237405e7f032b5c53a82d9eccf6161c291 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71314 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80864)Record last updated .