CVE-2026-64582

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • Kernel crash, vmalloc_to_page() returns NULL when vfree wins the
per-PTE race -> vm_insert_page(NULL) → GPF in validate_page_before_insert
  • 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: 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---

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 8, 2026
No patch confirmed yet.
generic

RDMA/rxe: Fix a use-after-free problem in rxe_mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e59a6aa89e0fcd1d0707832eb4654fd9ae7d31e6
generic

RDMA/rxe: Fix a use-after-free problem in rxe_mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e038d42cc09ca1da9d3568ce8ae062b2bfb3bc0e
generic

RDMA/rxe: Fix a use-after-free problem in rxe_mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/665fb7d22a700c66a78db0cf88c6e6a649aba9d0
generic

RDMA/rxe: Fix a use-after-free problem in rxe_mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35744ab3d03c5fca8c1752f53fc8fc674e14c561
generic

RDMA/rxe: Fix a use-after-free problem in rxe_mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3525987a392536f31a484833af258971af63b24c

Vendor Advisories for CVE-2026-64582(1)

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

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)——
linux-6.12—6.12.100-1~deb12u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)7.1.5-1—

Data Freshness Timeline

(refreshed 28× in last 7d / 58× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:12 UTCGHSA enrichment
  3. 2026-08-20 06:19 UTCGHSA enrichment
  4. 2026-08-19 17:26 UTCEG score recompute
  5. 2026-08-19 17:26 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:56 UTCEG score recompute
  8. 2026-08-19 16:56 UTCGHSA enrichment
  9. 2026-08-19 10:43 UTCGHSA enrichment
  10. 2026-08-18 21:43 UTCGHSA enrichment
  11. 2026-08-18 08:39 UTCGHSA enrichment
  12. 2026-08-17 19:32 UTCEG score recompute
  13. 2026-08-17 19:32 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:41 UTCEG score recompute
  16. 2026-08-17 05:41 UTCGHSA enrichment
  17. 2026-08-17 05:13 UTCEG score recompute
  18. 2026-08-17 05:13 UTCGHSA enrichment
  19. 2026-08-16 16:25 UTCEG score recompute
  20. 2026-08-16 16:25 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 03:33 UTCEG score recompute
  23. 2026-08-16 03:33 UTCGHSA enrichment
  24. 2026-08-15 14:41 UTCGHSA enrichment
  25. 2026-08-15 01:48 UTCEG score recompute
Show 33 more
  1. 2026-08-15 01:48 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 12:55 UTCGHSA enrichment
  4. 2026-08-14 00:03 UTCEG score recompute
  5. 2026-08-14 00:03 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 11:10 UTCGHSA enrichment
  8. 2026-08-12 22:17 UTCEG score recompute
  9. 2026-08-12 22:17 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 09:25 UTCGHSA enrichment
  12. 2026-08-11 20:32 UTCEG score recompute
  13. 2026-08-11 20:32 UTCGHSA enrichment
  14. 2026-08-11 07:39 UTCEG score recompute
  15. 2026-08-11 07:39 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 18:47 UTCGHSA enrichment
  18. 2026-08-10 05:54 UTCGHSA enrichment
  19. 2026-08-09 17:02 UTCEG score recompute
  20. 2026-08-09 17:02 UTCGHSA enrichment
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-09 04:09 UTCEG score recompute
  23. 2026-08-09 04:09 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 15:17 UTCEG score recompute▲ 7.80
  26. 2026-08-08 15:17 UTCGHSA enrichment
  27. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  28. 2026-08-08 06:22 UTCEG score recompute
  29. 2026-08-08 06:22 UTCGHSA enrichment
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-05 12:24 UTCNVD update
  32. 2026-08-05 11:47 UTCEG score recompute
  33. 2026-08-05 11:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64582?
CVE-2026-64582 is a high vulnerability published on August 5, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix a use-after-free problem in rxe_mmap rxemmap() removes a rxemmapinfo struct from the pendingmmaps list and releases pending_lock while the struct's kref is still at 1: listdelinit(&ip->pending_mmaps);…
When was CVE-2026-64582 disclosed?
CVE-2026-64582 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64582 actively exploited?
CVE-2026-64582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64582?
CVE-2026-64582 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64582?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64582, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64582?

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

Start Free Scan →Browse All CVEs