CVE-2026-64300
Last modified
CVE-2026-64300 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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().. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= b709eb872e19a19607bbb6d2975bc264d59735cf, < c8b7e113f7b61eef2f017e6329c27c2331058c5a; >= b709eb872e19a19607bbb6d2975bc264d59735cf, < 0cff05bd2186020f8706233e261016d149cc24db; >= b709eb872e19a19607bbb6d2975bc264d59735cf, < 5948aaf64f81f217a25dcc2bf6c0779bca19566c |
| Linux | Linux | 6.14 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64300?
How severe is CVE-2026-64300?
How do I fix CVE-2026-64300?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64294In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64295In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64296In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64297In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64298In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64299In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64301In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64302In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64303In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64304In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64305In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64306In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-64300?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
