{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.4-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  perf/aux: Fix page UAF in map_range()  map_range() reads rb-\u003eaux_pages[], rb-\u003eaux_nr_pages and rb-\u003eaux_pgoff via perf_mmap_to_page() while holding only event-\u003emmap_mutex. Those fields are serialized by rb-\u003eaux_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-\u003eaux_pages[0]   [2]: rb-\u003eaux_nr_pages++                                   [3]: perf_mmap_to_page()                                          returns rb-\u003eaux_pages[0]                                   [4]: map it as VM_PFNMAP   [5]: rb-\u003eaux_pgoff = 1    munmap the page   [6]: free rb-\u003eaux_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-\u003eaux_mutex across the page walk in map_range().",
  "id": "DEBIAN-CVE-2026-64300",
  "modified": "2026-09-14T16:47:44.907978364Z",
  "published": "2026-07-25T10:17:10.930Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64300"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64300"
  ]
}