CVE-2026-80864

UNRATEDCVSS · not yet scoredTrending — Patch released this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

Published

September 4, 2026

Last Modified

September 4, 2026

References (5)

Vendor Advisories for CVE-2026-80864(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-570.147.1.el9_62026-10-08redhat
redhatkernel-0:4.18.0-305.211.1.el8_42026-10-07redhat
redhatkernel-0:4.18.0-477.172.1.el8_82026-10-07redhat
redhatkernel-0:5.14.0-427.154.1.el9_42026-10-07redhat
redhatkernel-0:4.18.0-372.220.1.el8_62026-10-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (172 versions)
  • every version up to 7.1.13-1: fixed in 7.1.13-1
—

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-09 01:11 UTCVendor advisory
  3. 2026-10-09 01:11 UTCGHSA enrichment
  4. 2026-10-08 17:13 UTCEPSS rescore
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-05 16:39 UTCVendor advisory
  9. 2026-10-05 16:39 UTCGHSA enrichment
  10. 2026-10-04 23:22 UTCEPSS rescore
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-02 21:30 UTCVendor advisory
  13. 2026-10-02 21:30 UTCGHSA enrichment
  14. 2026-10-02 17:57 UTCEPSS rescore
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 02:42 UTCEG score recompute
  18. 2026-09-30 02:42 UTCVendor advisory
  19. 2026-09-30 02:42 UTCGHSA enrichment
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-27 13:48 UTCEPSS rescore
  22. 2026-09-26 22:11 UTCVendor advisory
  23. 2026-09-26 22:11 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 00:28 UTCEPSS rescore
Show 27 more
  1. 2026-09-24 14:04 UTCEPSS rescore
  2. 2026-09-24 03:31 UTCVendor advisory
  3. 2026-09-24 03:31 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:01 UTCEPSS rescore
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-21 08:50 UTCGHSA enrichment
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 13:48 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 19:07 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-13 00:26 UTCGHSA enrichment
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-10 05:45 UTCGHSA enrichment
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 11:05 UTCEG score recompute
  22. 2026-09-07 11:05 UTCGHSA enrichment
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-05 15:31 UTCEPSS rescore
  25. 2026-09-04 16:22 UTCNVD update
  26. 2026-09-04 16:05 UTCEG score recompute
  27. 2026-09-04 16:04 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Same vendor

3 shown

redhat:RHSA-2026:77216 · redhat:RHSA-2026:77218

Frequently asked(4)

What is CVE-2026-80864?
CVE-2026-80864 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix responder UAF on IBQPMAXDESTRDATOMIC modifyqp rxeqpfromattr() handles IBQPMAXDESTRDATOMIC outside the IBQPSTATE path, so it holds no state_lock and runs while the responder task rxereceiver() (recvtask on rxewq) is…
When was CVE-2026-80864 disclosed?
CVE-2026-80864 was first published on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80864 actively exploited?
CVE-2026-80864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80864?
A fix for CVE-2026-80864 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80864 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80864

Explore →

Is Your Infrastructure Affected by CVE-2026-80864?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs