Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap

Noroxi assessment

Priority: Monitor (action score 31/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).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3371f2036e0f970166bbb624e25bba46d32fa18e, 3525987a392536f31a484833af258971af63b24c, 35744ab3d03c5fca8c1752f53fc8fc674e14c561; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.

Low priority for now. Upgrade to Linux Linux 3371f2036e0f970166bbb624e25bba46d32fa18e, 3525987a392536f31a484833af258971af63b24c, 35744ab3d03c5fca8c1752f53fc8fc674e14c561; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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 a use-after-free problem in rxe_mmap rxe_mmap() removes a rxe_mmap_info struct from the pending_mmaps list and releases pending_lock while the struct's kref is still at 1: list_del_init(&ip->pending_mmaps); spin_unlock_bh(&rxe->pending_lock); /* ref == 1, no lock held */ ret = remap_vmalloc_range(vma, ip->obj, 0); /* walks PTEs */ [...] rxe_vma_open(vma); /* kref_get, ref → 2 */ remap_vmalloc_range_partial() walks PTEs without any lock. A concurrent DESTROY_CQ ioctl on another CPU calls: kref_put(&q->ip->ref, rxe_mmap_release) /* ref 1→0 */ vfree(ip->obj) /* clears vmalloc PTEs mid-walk */ kfree(ip) /* frees rxe_mmap_info */ This yields: 1. Kernel crash, vmalloc_to_page() returns NULL when vfree wins the per-PTE race -> vm_insert_page(NULL) → GPF in validate_page_before_insert 2. Page UAF, vmalloc_to_page() reads a stale PTE before vfree clears it. User VMA holds a PTE to a free'd page which might eventually get reallocated later by vmalloc which allows the attacker to get a clean page-level UAF. It is worth noting that even though a page-level UAF is possible given the strong primitive, it is statistically very difficult to achieve given the very short time window (after the last insert_page and before the kref_get). The call trace are as below: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 0 UID: 1000 PID: 413 Comm: poc Not tainted 7.0.0-rc5-dirty #28 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:validate_page_before_insert+0x32/0x300 Code: e5 41 57 41 56 49 89 fe 41 55 41 54 53 48 89 f3 e8 93 b5 a3 ff 48 8d 7b 08 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7b 02 00 00 4c 8b 63 08 31 ff 4d 89 e5 41 83 e5 RSP: 0018:ffff88811b15f2f0 EFLAGS: 00000202 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000008 RBP: ffff88811b15f318 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881181eee00 R13: 0000000000000000 R14: ffff8881181eee00 R15: ffff8881181eee20 FS: 00007b1e000f76c0(0000) GS:ffff8884268e0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007b1e00a24ac0 CR3: 0000000116eb3000 CR4: 00000000000006f0 Call Trace: <TASK> insert_page+0x8f/0x190 ? __pfx_insert_page+0x10/0x10 ? kasan_save_alloc_info+0x38/0x60 vm_insert_page+0x2e7/0x400 remap_vmalloc_range_partial+0x212/0x3e0 remap_vmalloc_range+0x6e/0xb0 ? __kasan_check_write+0x14/0x30 rxe_mmap+0x2e9/0x5d0 ib_uverbs_mmap+0x1ad/0x2c0 __mmap_region+0x12c2/0x2ad0 ? __pfx___mmap_region+0x10/0x10 ? __sanitizer_cov_trace_switch+0x58/0xb0 ? mas_prev_slot+0x360/0x39c0 ? __sanitizer_cov_trace_switch+0x58/0xb0 ? mas_next_slot+0x1e5b/0x2f40 ? __sanitizer_cov_trace_cmp8+0x18/0x30 ? unmapped_area_topdown+0x4dd/0x610 ? kfree+0x1b1/0x440 ? free_cpumask_var+0x16/0x30 ? __kasan_slab_free+0x7d/0xa0 ? __sanitizer_cov_trace_cmp8+0x18/0x30 mmap_region+0x2e6/0x3c0 do_mmap+0xa3e/0x12a0 ? __pfx_do_mmap+0x10/0x10 ? __kasan_check_write+0x14/0x30 ? down_write_killable+0xba/0x160 ? __pfx_down_write_killable+0x10/0x10 ? __sanitizer_cov_trace_cmp4+0x16/0x30 vm_mmap_pgoff+0x2d4/0x4a0 ? __pfx_vm_mmap_pgoff+0x10/0x10 ? fget+0x1bf/0x270 ksys_mmap_pgoff+0x40c/0x690 ? __sanitizer_cov_trace_const_cmp4+0x16/0x30 ? __pfx_ksys_mmap_pgoff+0x10/0x10 ? __kasan_check_write+0x14/0x30 ? _raw_spin_trylock+0xbb/0x130 ? __pfx__raw_spin_trylock+0x10/0x10 __x64_sys_mmap+0x135/0x1e0 x64_sys_c ---truncated---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 5, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-64582

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 b810352d0916796dabe633cdb9adee9863ab4911affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before aef5ea8578f97f2701039600846a8bcf5f21e863affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 3371f2036e0f970166bbb624e25bba46d32fa18eaffected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 665fb7d22a700c66a78db0cf88c6e6a649aba9d0affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before e038d42cc09ca1da9d3568ce8ae062b2bfb3bc0eaffected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before e59a6aa89e0fcd1d0707832eb4654fd9ae7d31e6affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 3525987a392536f31a484833af258971af63b24caffected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 35744ab3d03c5fca8c1752f53fc8fc674e14c561affected · git
    • before 4.8not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10

+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-64580Aug 5, 2026 · xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst()
    31Monitor
  • ← EarlierCVE-2026-64581Aug 5, 2026 · xfrm: fix sk_dst_cache double-free in xfrm_user_policy()
    31Monitor
  • Later →CVE-2026-64583Aug 6, 2026 · usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown
    31Monitor

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 Linux3371f2036e0f970166bbb624e25bba46d32fa18eVendor (CNA)
Linux Linux3525987a392536f31a484833af258971af63b24cVendor (CNA)
Linux Linux35744ab3d03c5fca8c1752f53fc8fc674e14c561Vendor (CNA)
Linux Linux665fb7d22a700c66a78db0cf88c6e6a649aba9d0Vendor (CNA)
Linux Linuxaef5ea8578f97f2701039600846a8bcf5f21e863Vendor (CNA)
Linux Linuxb810352d0916796dabe633cdb9adee9863ab4911Vendor (CNA)
Linux Linuxe038d42cc09ca1da9d3568ce8ae062b2bfb3bc0eVendor (CNA)
Linux Linuxe59a6aa89e0fcd1d0707832eb4654fd9ae7d31e6Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+7

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.

  • CVE-2026-645641 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing
    39Monitor
  • CVE-2026-681175 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
    39Monitor
  • CVE-2026-681445 days apartphonet: pep: fix use-after-free in pep_get_sb()
    39Monitor
  • CVE-2026-681565 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
    39Monitor
  • CVE-2026-683815 days apartksmbd: pin conn during async oplock break notification
    39Monitor
  • CVE-2026-684265 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records