CVE-2026-23127
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2026-23127 is a refcount warning vulnerability in the Linux kernel's perf subsystem, triggered when refcount_inc(&event->mmap_count) is called inside perf_mmap_rb() while mmap_count equals zero, producing a "addition on 0; use-after-free" kernel warning. It affects Linux kernel versions 6.18 through 6.18.7 and 6.19-rc1 through 6.19-rc6. The vulnerability was published on February 14, 2026, with patches added to the stable kernel repositories on March 18, 2026. It carries a CVSS v3.1 base score of 5.5 (Medium) (Feedly, Tenable).

Technical details

The root cause is improper reference counting (CWE-911 / use-after-free warning) in the Linux kernel perf subsystem. When a group member perf event is created with the PERF_FLAG_FD_OUTPUT flag, perf_event_set_output() copies the output event's ring buffer (event->rb), causing perf_mmap_rb() to call refcount_inc(&event->mmap_count) when mmap_count is still 0 — a state that should be disallowed. The fix disallows incrementing the refcount when event->mmap_count == 0, which also prevents two events from concurrently updating the same user_page. The attack vector is local, requires low privileges, and has low attack complexity (Feedly, Kernel Patch 1).

Impact

Successful exploitation results in high availability impact — a low-privileged local user can trigger kernel warnings and potential system instability or denial-of-service conditions through refcount corruption in the perf subsystem. There is no confidentiality or integrity impact, and the scope is unchanged (confined to the affected kernel). The vulnerability does not enable privilege escalation or data exfiltration based on current analysis (Feedly).

Exploitation steps

  1. Setup: Obtain a local account with low privileges on a system running Linux kernel 6.18–6.18.7 or 6.19-rc1 through 6.19-rc6.
  2. Open group leader event: Call perf_event_open with a zeroed perf_event_attr struct targeting PID 0 and CPU -1, storing the returned file descriptor as fd.
  3. Map the group leader: Call mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0) to establish the ring buffer for the leader event, setting mmap_count appropriately.
  4. Open group member with FD_OUTPUT: Call perf_event_open again with the same attr, passing fd as the group leader and the PERF_FLAG_FD_OUTPUT flag, storing the result as victim. This causes perf_event_set_output() to copy event->rb from the leader.
  5. Map the group member: Call mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, victim, 0). This triggers perf_mmap_rb() to call refcount_inc(&event->mmap_count) when mmap_count == 0, generating the kernel warning and potential instability (Feedly).

Indicators of compromise

  • Logs: Kernel log (dmesg / /var/log/kern.log) entries containing refcount_t: addition on 0; use-after-free and WARNING: lib/refcount.c:25 associated with the perf subsystem.
  • Process: Unusual or repeated calls to perf_event_open syscall (syscall number 298 on x86_64) from unprivileged processes, particularly with PERF_FLAG_FD_OUTPUT flag set, followed by mmap on the resulting file descriptors.
  • System Behavior: Unexpected kernel warnings or soft lockups on systems not under active performance monitoring workloads (Feedly).

Mitigation and workarounds

Update the Linux kernel to version 6.18.8 or later, which includes the fix disallowing refcount_inc when event->mmap_count == 0. Patches are available in the Linux stable kernel repository at commits 23c0e4bd93d0 and d06bf78e55d5 (Kernel Patch 1, Kernel Patch 2). As a temporary workaround on systems that cannot be patched immediately, restrict unprivileged user access to perf events by setting kernel.perf_event_paranoid to a higher value (e.g., sysctl -w kernel.perf_event_paranoid=3) to limit exposure, though this does not fully eliminate the vulnerability (Feedly).

Community reactions

The vulnerability received limited public attention, with automated aggregation on platforms such as VulnDB (via infosec.exchange) and standard CVE tracking sites. No notable researcher commentary, vendor statements beyond the kernel patch, or significant media coverage has been identified (Feedly).

Additional resources


SourceThis report was generated using AI

Related Linux Kernel vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-64557NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-selftests-internal
NoNoJul 29, 2026
CVE-2026-64556NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-64k-devel
NoNoJul 29, 2026
CVE-2026-64555NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-azure-fde-6.14
NoNoJul 27, 2026
CVE-2026-64554NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-gcp-6.14
NoYesJul 27, 2026
CVE-2026-64553NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-64k-debug-modules-internal
NoYesJul 27, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management