cve.bz

CVE-2026-89791 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.18.52
  • Linux Linux: fixed in 7.2.5
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Red Hat, SUSE, openSUSE, AlmaLinux, Rocky Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89791 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89791?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89791?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89791 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.18 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.52
Linux7.27.2.5
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.6-1DEBIAN-CVE-2026-89791
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89791
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89791
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89791
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-89791
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-89791 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-89791 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-89791 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-89791 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-89791 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 25 moreno fix listedUBUNTU-CVE-2026-89791
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-89791
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-89791 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:10.2rv, perf, rtla and 88 more0:6.12.0-211.68.1.el10_2RHSA-2026:88477
Red Hatenterprise_linux:10.3rv, perf, rtla and 89 more0:6.12.0-264.14.1.el10_3RHSA-2026:98608
Red Hatshadow_migration_toolkit:10::el10kernel-modules-internal0:6.12.0-211.68.1.el10_2RHSA-2026:88477
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.39.1SUSE-SU-2026:24197-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.39.1SUSE-SU-2026:24235-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.39.1.160000.2.26SUSE-SU-2026:24235-1
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.6.1SUSE-SU-2026:24691-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.39.1.160000.2.26SUSE-SU-2026:24184-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.39.1SUSE-SU-2026:24184-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.39.1SUSE-SU-2026:24179-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.39.1.160000.2.25openSUSE-SU-2026:22091-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.39.1openSUSE-SU-2026:22091-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.68.1.el10_2ALSA-2026:88477
Rocky Linux10kernel0:6.12.0-211.68.1.el10_2RLSA-2026:88477
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89791

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A race condition in the Linux kernel's perf subsystem allows a local unprivileged user to escalate privileges to root, an impact rated IMPORTANT by Red Hat. perf_mmap_close() drops the ring buffer's mmap_count without holding event->mmap_mutex, so a concurrent perf mmap() revival can complete within that window; the closing path then frees the newly allocated ring buffer while another process still has it mapped, resulting in a page-level use-after-free. With the default kernel.perf_event_paranoid=2 setting, any unprivileged local user can trigger this race, and successful exploitation leads to full compromise of the confidentiality, integrity, and availability of the system. The kernel component in Red Hat Enterprise Linux 10.2.z, 10.3.z, and 10.4 and in Red Hat In-Vehicle OS 2.0.z and 2.1 (including the kernel-ivos-qualcomm variant) is affected, and a fix is being pursued in those streams. Other Red Hat Enterprise Linux kernel and kernel-rt streams and the RHEL CoreOS kernels shipped with OpenShift Container Platform are not affected because the vulnerable code is not present in those kernels. Red Hat assigns this flaw a CVSS 3.1 base score of 7.0 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), lower than the upstream score of 7.8, because reliable exploitation requires winning a narrow timing race between concurrent mmap() and munmap() operations, which Red Hat rates as high attack complexity.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.68.1.el10_2Fixed 2026-10-23RHSA-2026:88477
Red Hat Enterprise Linux 10kernel-0:6.12.0-264.14.1.el10_3Fixed 2026-11-11RHSA-2026:98608
Shadow Migration Toolkit for Virtualization for RHEL 10kernel-0:6.12.0-211.68.1.el10_2Fixed 2026-10-23RHSA-2026:88477
Red Hat Enterprise Linux 6kernelUnder investigation
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-89791.

References

Check your stackJSON