CVE-2026-64300
Vulnerability Summary
Timeline
Description
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 Metrics
- v4.0•HIGH•Score: 7.3CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Trends
Current EPSS score: 0.18%• Percentile: 8%
Techniques & Countermeasures
- CWE-416•Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected Systems
- debian•linux
< 7.1.4-1
- ubuntu•linux
all | < 7.0.0-31.31
- ubuntu•linux-allwinner-5.19
all
- ubuntu•linux-aws
all | < 7.0.0-1012.12
- ubuntu•linux-aws-5.0
all
- ubuntu•linux-aws-5.11
all
- ubuntu•linux-aws-5.13
all
- ubuntu•linux-aws-5.19
all
- ubuntu•linux-aws-5.3
all
- ubuntu•linux-aws-5.8
all
- ubuntu•linux-aws-6.14
all
- ubuntu•linux-aws-6.17
all
- ubuntu•linux-aws-6.2
all
- ubuntu•linux-aws-6.5
all
- ubuntu•linux-aws-7.0
all | < 7.0.0-1012.12~24.04.1
- ubuntu•linux-azure
all | all
- ubuntu•linux-azure-5.11
all
- ubuntu•linux-azure-5.13
all
- ubuntu•linux-azure-5.19
all
- ubuntu•linux-azure-5.3
all
- ubuntu•linux-azure-5.8
all
- ubuntu•linux-azure-6.11
all
- ubuntu•linux-azure-6.14
all
- ubuntu•linux-azure-6.17
all
- ubuntu•linux-azure-6.2
all
- ubuntu•linux-azure-6.5
all
- ubuntu•linux-azure-7.0
all
- ubuntu•linux-azure-edge
all
- ubuntu•linux-azure-fde
all | all
- ubuntu•linux-azure-fde-5.19
all
- ubuntu•linux-azure-fde-6.14
all
- ubuntu•linux-azure-fde-6.2
all
- ubuntu•linux-azure-fde-7.0
all
- ubuntu•linux-azure-nvidia-6.14
all
- ubuntu•linux-bluefield
all
- ubuntu•linux-gcp
all | all | < 7.0.0-1011.11
- ubuntu•linux-gcp-5.11
all
- ubuntu•linux-gcp-5.13
all
- ubuntu•linux-gcp-5.19
all
- ubuntu•linux-gcp-5.3
all
- ubuntu•linux-gcp-5.8
all
- ubuntu•linux-gcp-6.11
all
- ubuntu•linux-gcp-6.14
all
- ubuntu•linux-gcp-6.17
all
- ubuntu•linux-gcp-6.2
all
- ubuntu•linux-gcp-6.5
all
- ubuntu•linux-gcp-7.0
all | < 7.0.0-1011.11~24.04.1
- ubuntu•linux-gke
all | all | < 7.0.0-1006.7
- ubuntu•linux-gke-4.15
all
- ubuntu•linux-gke-5.15
all
Showing first 50 affected entries in server-rendered view.
References (12)
- https://git.kernel.org/stable/c/c8b7e113f7b61eef2f017e6329c27c2331058c5a
- https://git.kernel.org/stable/c/0cff05bd2186020f8706233e261016d149cc24db
- https://git.kernel.org/stable/c/5948aaf64f81f217a25dcc2bf6c0779bca19566c
- https://ubuntu.com/security/CVE-2026-64300
- https://www.cve.org/CVERecord?id=CVE-2026-64300
- https://git.kernel.org/linus/5948aaf64f81f217a25dcc2bf6c0779bca19566c
- https://security-tracker.debian.org/tracker/CVE-2026-64300
- https://ubuntu.com/security/notices/USN-8726-1
- https://ubuntu.com/security/notices/USN-8727-1
- https://ubuntu.com/security/notices/USN-8728-1
- https://ubuntu.com/security/notices/USN-8760-1
- https://ubuntu.com/security/notices/USN-8726-2