CVE-2026-64582

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — 4 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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 8, 2026
Patch available.
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(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.166.1.rt7.507.el8_102026-09-22redhat
redhatkernel-0:4.18.0-553.166.1.el8_102026-09-22redhat
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat

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

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

(refreshed 24× in last 7d / 118× 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.

Showing the most recent 100 of 245 total refreshes for this CVE.

  1. 2026-10-04 23:34 UTCVendor advisory
  2. 2026-10-04 23:34 UTCGHSA enrichment
  3. 2026-10-04 06:03 UTCEG score recompute
  4. 2026-10-04 06:03 UTCVendor advisory
  5. 2026-10-04 06:03 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 01:10 UTCEG score recompute
  8. 2026-10-03 01:10 UTCVendor advisory
  9. 2026-10-03 01:10 UTCGHSA enrichment
  10. 2026-10-02 17:56 UTCEPSS rescore
  11. 2026-10-02 09:59 UTCEG score recompute
  12. 2026-10-02 09:59 UTCVendor advisory
  13. 2026-10-02 09:59 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 15:15 UTCVendor advisory
  16. 2026-10-01 15:15 UTCGHSA enrichment
  17. 2026-10-01 02:20 UTCEG score recompute
  18. 2026-10-01 02:20 UTCVendor advisory
  19. 2026-10-01 02:20 UTCGHSA enrichment
  20. 2026-09-30 15:03 UTCEPSS rescore
  21. 2026-09-29 06:19 UTCEG score recompute
  22. 2026-09-29 06:19 UTCVendor advisory
  23. 2026-09-29 06:19 UTCGHSA enrichment
  24. 2026-09-28 13:51 UTCEPSS rescore
  25. 2026-09-28 06:35 UTCVendor advisory
Show 75 more
  1. 2026-09-28 06:35 UTCGHSA enrichment
  2. 2026-09-27 17:43 UTCEG score recompute
  3. 2026-09-27 17:43 UTCVendor advisory
  4. 2026-09-27 17:43 UTCGHSA enrichment
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-25 04:33 UTCEG score recompute
  7. 2026-09-25 04:33 UTCVendor advisory
  8. 2026-09-25 04:33 UTCGHSA enrichment
  9. 2026-09-24 05:53 UTCEG score recompute
  10. 2026-09-24 05:53 UTCVendor advisory
  11. 2026-09-24 05:53 UTCGHSA enrichment
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-23 17:00 UTCVendor advisory
  14. 2026-09-23 17:00 UTCGHSA enrichment
  15. 2026-09-23 04:02 UTCEG score recompute
  16. 2026-09-23 04:02 UTCVendor advisory
  17. 2026-09-23 04:01 UTCGHSA enrichment
  18. 2026-09-22 15:07 UTCVendor advisory
  19. 2026-09-22 15:07 UTCGHSA enrichment
  20. 2026-09-22 01:39 UTCEG score recompute
  21. 2026-09-22 01:39 UTCVendor advisory
  22. 2026-09-22 01:39 UTCGHSA enrichment
  23. 2026-09-20 20:49 UTCEG score recompute
  24. 2026-09-20 20:49 UTCVendor advisory
  25. 2026-09-20 20:49 UTCGHSA enrichment
  26. 2026-09-20 20:16 UTCEPSS rescore
  27. 2026-09-19 23:17 UTCEG score recompute
  28. 2026-09-19 23:17 UTCVendor advisory
  29. 2026-09-19 23:17 UTCGHSA enrichment
  30. 2026-09-19 07:49 UTCEG score recompute
  31. 2026-09-19 07:49 UTCVendor advisory
  32. 2026-09-19 07:49 UTCGHSA enrichment
  33. 2026-09-18 19:28 UTCEPSS rescore
  34. 2026-09-18 17:43 UTCVendor advisory
  35. 2026-09-18 17:43 UTCGHSA enrichment
  36. 2026-09-18 04:50 UTCEG score recompute
  37. 2026-09-18 04:50 UTCVendor advisory
  38. 2026-09-18 04:50 UTCGHSA enrichment
  39. 2026-09-17 15:57 UTCVendor advisory
  40. 2026-09-17 15:57 UTCGHSA enrichment
  41. 2026-09-17 01:07 UTCEG score recompute
  42. 2026-09-17 01:07 UTCVendor advisory
  43. 2026-09-17 01:07 UTCGHSA enrichment
  44. 2026-09-16 14:08 UTCEPSS rescore
  45. 2026-09-16 05:15 UTCEPSS rescore
  46. 2026-09-16 03:15 UTCVendor advisory
  47. 2026-09-16 03:15 UTCGHSA enrichment
  48. 2026-09-15 06:51 UTCEG score recompute
  49. 2026-09-15 06:51 UTCVendor advisory
  50. 2026-09-15 06:51 UTCGHSA enrichment
  51. 2026-09-14 16:52 UTCVendor advisory
  52. 2026-09-14 16:51 UTCGHSA enrichment
  53. 2026-09-14 03:58 UTCEG score recompute
  54. 2026-09-14 03:58 UTCVendor advisory
  55. 2026-09-14 03:58 UTCGHSA enrichment
  56. 2026-09-13 15:05 UTCVendor advisory
  57. 2026-09-13 15:05 UTCGHSA enrichment
  58. 2026-09-13 02:10 UTCEG score recompute
  59. 2026-09-13 02:10 UTCVendor advisory
  60. 2026-09-13 02:10 UTCGHSA enrichment
  61. 2026-09-12 13:16 UTCVendor advisory
  62. 2026-09-12 13:16 UTCGHSA enrichment
  63. 2026-09-12 00:23 UTCEG score recompute
  64. 2026-09-12 00:23 UTCVendor advisory
  65. 2026-09-12 00:23 UTCGHSA enrichment
  66. 2026-09-11 14:53 UTCEPSS rescore
  67. 2026-09-11 09:58 UTCEG score recompute
  68. 2026-09-11 09:58 UTCGHSA enrichment
  69. 2026-09-11 09:37 UTCEPSS rescore
  70. 2026-09-10 21:03 UTCEG score recompute
  71. 2026-09-10 21:03 UTCGHSA enrichment
  72. 2026-09-10 08:10 UTCGHSA enrichment
  73. 2026-09-09 19:17 UTCVendor advisory
  74. 2026-09-09 19:17 UTCGHSA enrichment
  75. 2026-09-09 06:25 UTCEG score recompute

Related CVEs(same vendor)

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 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.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64582?
CVE-2026-64582 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64582?
A fix for CVE-2026-64582 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64582 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-64582

Explore →

Is Your Infrastructure Affected by CVE-2026-64582?

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

Book a Demo →Browse All CVEs