CVE-2026-89791

published 16 Sep 2026 · updated 15 Nov 2026

perf: Fix use-after-free when perf mmap() revival races with the last munmap()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c739f54f1c77f3a4643160cd2e031b6c2f2aab6, Kernel 58a8108bc73de0740d5b88150465d6690ea5f85f, Kernel 929cb3b9dc818dd9fa89d510d4ff2b255e42badd and 2 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.18, >=59741451b49ce9964a9758c19d6f7df2a1255c75 <0c739f54f1c77f3a4643160cd2e031b6c2f2aab6, >=59741451b49ce9964a9758c19d6f7df2a1255c75 <58a8108bc73de0740d5b88150465d6690ea5f85f, >=59741451b49ce9964a9758c19d6f7df2a1255c75 <929cb3b9dc818dd9fa89d510d4ff2b255e42badd0c739f54f1c77f3a4643160cd2e031b6c2f2aab6, 58a8108bc73de0740d5b88150465d6690ea5f85f, 929cb3b9dc818dd9fa89d510d4ff2b255e42badd
linux-kernel: Kernel>=6.18.0 <6.18.52, >=6.19.0 <7.2.56.18.52, 7.2.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89791 severity on Zeptric[![CVE-2026-89791](https://zeptric.io/badge/cve/CVE-2026-89791.svg)](https://zeptric.io/cve/CVE-2026-89791)