CVE-2026-23127: perf: Fix refcount warning on event->mmap_count increment
In the Linux kernel, the following vulnerability has been resolved:
perf: Fix refcount warning on event->mmap_count increment
When calling refcount_inc(&event->mmap_count) inside perf_mmap_rb(), the
following warning is triggered:
refcount_t: addition on 0; use-after-free.
WARNING: lib/refcount.c:25
PoC:
struct perf_event_attr attr = {0};
int fd = syscall(__NR_perf_event_open, &attr, 0, -1, -1, 0);
mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
int victim = syscall(__NR_perf_event_open, &attr, 0, -1, fd,
PERF_FLAG_FD_OUTPUT);
mmap(NULL, 0x3000, PROT_READ | PROT_WRITE, MAP_SHARED, victim, 0);
This occurs when creating a group member event with the flag
PERF_FLAG_FD_OUTPUT. The group leader should be mmap-ed and then mmap-ing
the event triggers the warning.
Since the event has copied the output_event in perf_event_set_output(),
event->rb is set. As a result, perf_mmap_rb() calls
refcount_inc(&event->mmap_count) when event->mmap_count = 0.
Disallow the case when event->mmap_count = 0. This also prevents two
events from updating the same user_page.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects perf event memory mapping. A crafted local perf setup can trigger a refcount warning tied to use-after-free protection, indicating unsafe lifetime handling. The public data does not provide CVSS, CWE, or confirmed impact beyond the kernel fix description.
Executive priority
Treat as a kernel maintenance priority, especially for shared Linux infrastructure. Urgency is lower than a known-exploited remote issue, but kernel lifetime bugs deserve prompt patch tracking because final impact may be clarified later.
Technical view
The flaw is in perf_mmap_rb() when refcount_inc() is called on event->mmap_count after perf_event_set_output() copies an output_event. A group member using PERF_FLAG_FD_OUTPUT can reach event->mmap_count equal to zero, so the fix disallows that case and prevents two events updating the same user_page.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or affected downstream builds with the perf code present. The bundle lists Linux kernel 6.18-era affected data and stable kernel fix commits. Distribution-specific backport status is not provided.
Exploitation context
No KEV listing is reported, and the provided sources do not state active exploitation. The source description includes a proof-of-concept pattern, but available evidence only supports a local kernel perf trigger, not remote exploitation or confirmed privilege escalation.
Researcher notes
Evidence is narrow: a Linux kernel perf refcount warning and a fix that rejects mmap_count zero in this path. Do not assume broader exploitability without additional kernel analysis or vendor advisories. Assess local perf access and fixed commit presence.
Mitigation direction
Check your Linux vendor advisory for CVE-2026-23127 coverage and backport status.
Update to a kernel build containing the referenced stable fixes.
Review local perf_event_open access controls where untrusted local users exist.
Prioritize shared multi-user Linux hosts and container platforms using affected kernels.
Validation and detection
Inventory kernel versions across Linux hosts and map them to vendor fixed builds.
Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
Check whether untrusted users can access perf_event_open on exposed systems.
Track CVE metadata for CVSS, CWE, and distribution advisories as they appear.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23127 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.