CVE-2026-64582

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-53329 (ENISA EUVD) · GHSA-9mqw-m8jv-5hmw (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%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
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Aug 8, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(10)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-27ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-27ubuntu
redhatkernel-0:5.14.0-570.147.1.el9_62026-10-08redhat
redhatkernel-0:5.14.0-427.154.1.el9_42026-10-07redhat
redhatkernel-0:4.18.0-477.172.1.el8_82026-10-07redhat
redhatkernel-0:4.18.0-372.220.1.el8_62026-10-07redhat
redhatkernel-0:4.18.0-305.211.1.el8_42026-10-07redhat
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
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

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 9× in last 7d / 62× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 301 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64582?
CVE-2026-64582 is a high-severity vulnerability; its CVE record was 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 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);…
When was the CVE record for CVE-2026-64582 published?
The CVE record for CVE-2026-64582 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-64582 actively exploited?
CVE-2026-64582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th 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