Vulnerability · Published Sep 16, 2026 · Assigned by Linux
CVE-2026-89791perf: Fix use-after-free when perf mmap() revival races with the last munmap()
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: perf: Fix use-after-free when perf mmap() revival races with the last munmap() perf_mmap_close() drops rb->mmap_count *without* holding event->mmap_mutex (the refcount_dec_and_test() right before the refcount_dec_and_mutex_lock() of event->mmap_count). A concurrent perf_mmap_rb() can slot its entire "revival" path into that window (perf_mmap holds event->mmap_mutex for its whole duration, including rb_alloc): munmap side (perf_mmap_close) mmap side (perf_mmap_rb) ----------------------------------- -------------------------------- rb->mmap_count 1 -> 0 (no lock) (holds event->mmap_mutex) inc_not_zero(rb->mmap_count) fails ring_buffer_attach(event, NULL) rb_alloc() + attach new rb refcount_set(&event->mmap_count, 1) lock; event->mmap_count 1 -> 0 ring_buffer_attach(event, NULL) ring_buffer_put() -> frees the *new* rb The revival's refcount_set(&event->mmap_count, 1) is an invisible 1 -> 1 write: the close frees the just-revived buffer although the other process still has it mapped -- a page-level use-after-free allowing local privilege escalation to root by any unprivileged user (default kernel.perf_event_paranoid=2). Swap the order of the two counter updates: event->mmap_count is dropped first via refcount_dec_and_mutex_lock(), so its 1 -> 0 transition and the ring_buffer_attach() stay serialized with perf_mmap(). rb->mmap_count == 0 then implies every event using the buffer is detached already, so the result of the rb->mmap_count drop can gate the remaining teardown directly and detach_rest is no longer needed. An earlier fix for this race from Kyle Zeng and David Lee takes event->mmap_mutex around both counter updates [0]; here the not-last close stays lockless.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | kernel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-devel-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-64k-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-abi-stablelists | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-cross-headers | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-devel-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-debug-uki-virt | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-devel-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-doc | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-headers | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-modules-extra-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-64k-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-debug-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-rt-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-tools | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-tools-libs | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-tools-libs-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-uki-virt | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-uki-virt-addons | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-devel | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-devel-matched | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-modules | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-modules-core | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | kernel-zfcpdump-modules-extra | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | libperf | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | perf | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | python3-perf | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | rtla | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| AlmaLinux:10 | rv | 6.12.0-211.68.1.el10_2 | ALSA-2026:88477 |
| Debian:14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-89791 |
| Rocky Linux:10 | kernel | 0:6.12.0-211.68.1.el10_2 | RLSA-2026:88477 |
| Ubuntu:26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1016.17 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1016.18 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1017.17 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1017.17 | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1015.16 | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-42.42.1 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-89791 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-89791 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 59741451b49ce9964a9758c19d6f7df2a1255c75 – before 929cb3b9dc818dd9fa89d510d4ff2b255e42badd59741451b49ce9964a9758c19d6f7df2a1255c75 – before 0c739f54f1c77f3a4643160cd2e031b6c2f2aab659741451b49ce9964a9758c19d6f7df2a1255c75 – before 58a8108bc73de0740d5b88150465d6690ea5f85f |
| Linux | Linux | 6.18 |