Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 0136b528b753c5a56e4d997ef20b86bb6750b8fb, 60dfd47929cd1e7070daa810d40ce538d888410d, 6f7014237405e7f032b5c53a82d9eccf6161c291; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 0136b528b753c5a56e4d997ef20b86bb6750b8fb, 60dfd47929cd1e7070daa810d40ce538d888410d, 6f7014237405e7f032b5c53a82d9eccf6161c291; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80864

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.8affected
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 87e40635d77aa19088550698c81eb295d5131f71affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 82257379061c0a7aba6c77081d988339982af115affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 0136b528b753c5a56e4d997ef20b86bb6750b8fbaffected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before ffa4f0be69656be1755090f02db38d49816585c6affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before d4cd32eb8bd2b0ffbdc7b1f3d82ce6a371f8f844affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 60dfd47929cd1e7070daa810d40ce538d888410daffected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 6f7014237405e7f032b5c53a82d9eccf6161c291affected · git
    • before 4.8not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.1.13-17.1.13-1
Red Hat:rhel_aus:8.4::baseosbpftoolbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseosbpftool-debuginfobefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernelbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-abi-stablelistsbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-corebefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debugbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-corebefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-debuginfobefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-develbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modulesbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modules-extrabefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfobefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-develbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-docbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modulesbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modules-extrabefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-toolsbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-debuginfobefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-libsbefore 0:4.18.0-305.211.1.el8_40:4.18.0-305.211.1.el8_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80862Sep 4, 2026 · nvme-tcp: fix usage of page_frag_cache
    0Monitor
  • ← EarlierCVE-2026-80863Sep 4, 2026 · RDMA/rxe: Fix OOB in free_rd_atomic_resources()
    0Monitor
  • Later →CVE-2026-80866Sep 4, 2026 · tipc: avoid busy looping in tipc_exit_net()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0136b528b753c5a56e4d997ef20b86bb6750b8fbVendor (CNA)
Linux Linux60dfd47929cd1e7070daa810d40ce538d888410dVendor (CNA)
Linux Linux6f7014237405e7f032b5c53a82d9eccf6161c291Vendor (CNA)
Linux Linux82257379061c0a7aba6c77081d988339982af115Vendor (CNA)
Linux Linux87e40635d77aa19088550698c81eb295d5131f71Vendor (CNA)
Linux Linuxd4cd32eb8bd2b0ffbdc7b1f3d82ce6a371f8f844Vendor (CNA)
Linux Linuxffa4f0be69656be1755090f02db38d49816585c6Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-305.211.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records