CVE-2026-64300

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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%CVSS: 7.8Exploit: None knownExposed: 0

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.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
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 41× in last 7d / 129× 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 129 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 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% probability of exploitation in the next 30 days, which ranks it in the top 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64300?
CVE-2026-64300 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64300, 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-64300

Explore →

Is Your Infrastructure Affected by CVE-2026-64300?

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

Start Free Scan →Browse All CVEs