CVE-2026-64300

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. 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.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:

perf/aux: Fix page UAF in map_range()

map_range() reads rb->aux_pages[], rb->aux_nr_pages and rb->aux_pgoff via perf_mmap_to_page() while holding only event->mmap_mutex. Those fields are serialized by rb->aux_mutex, and mmap_mutex is per event.

Thus, two events sharing one rb via PERF_EVENT_IOC_SET_OUTPUT can race rb_alloc_aux() with map_range(), leading to a page-UAF scenario as follows:

CPU 0 CPU 1 ===== ===== rb_alloc_aux() map_range() [1]: allocate rb->aux_pages[0] [2]: rb->aux_nr_pages++ [3]: perf_mmap_to_page() returns rb->aux_pages[0] [4]: map it as VM_PFNMAP [5]: rb->aux_pgoff = 1

munmap the page [6]: free rb->aux_pages[0]

Pages mapped as VM_PFNMAP have no refcount protection, so CPU 1 holds a mapping to a freed physical frame.

Fix this by taking rb->aux_mutex across the page walk in map_range().

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.2%
EPSS %ILE
7th
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

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available.
generic

perf/aux: Fix page UAF in map_range() - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf/aux: Fix page UAF in map_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5948aaf64f81f217a25dcc2bf6c0779bca19566c
generic

perf/aux: Fix page UAF in map_range() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cff05bd2186020f8706233e261016d149cc24db

Vendor Advisories for CVE-2026-64300(2)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-04ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-04ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-04ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-04ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-04ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-10-04ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-04ubuntu
redhatkernel-0:6.12.0-211.47.1.el10_22026-08-12redhat

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

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 17× in last 7d / 96× 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 293 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64300?
CVE-2026-64300 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: perf/aux: Fix page UAF in map_range() maprange() reads rb->auxpages[], rb->auxnrpages and rb->aux_pgoff via perfmmaptopage() while holding only event->mmapmutex. Those fields are serialized by rb->auxmutex, and mmapmutex is per…
When was CVE-2026-64300 disclosed?
CVE-2026-64300 was first published on July 25, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64300 actively exploited?
CVE-2026-64300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64300?
CVE-2026-64300 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-64300?
A fix for CVE-2026-64300 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64300 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-64300

Explore →

Is Your Infrastructure Affected by CVE-2026-64300?

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

Book a Demo →Browse All CVEs