CVE-2025-21895 Details
Description
In the Linux kernel, the following vulnerability has been resolved: perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list Syskaller triggers a warning due to prev_epc->pmu != next_epc->pmu in perf_event_swap_task_ctx_data(). vmcore shows that two lists have the same perf_event_pmu_context, but not in the same order. The problem is that the order of pmu_ctx_list for the parent is impacted by the time when an event/PMU is added. While the order for a child is impacted by the event order in the pinned_groups and flexible_groups. So the order of pmu_ctx_list in the parent and child may be different. To fix this problem, insert the perf_event_pmu_context to its proper place after iteration of the pmu_ctx_list. The follow testcase can trigger above warning: # perf record -e cycles --call-graph lbr -- taskset -c 3 ./a.out & # perf stat -e cpu-clock,cs -p xxx // xxx is the pid of a.out test.c void main() { int count = 0; pid_t pid; printf("%d running\n", getpid()); sleep(30); printf("running\n"); pid = fork(); if (pid == -1) { printf("fork error\n"); return; } if (pid == 0) { while (1) { count++; } } else { while (1) { count++; } } } The testcase first opens an LBR event, so it will allocate task_ctx_data, and then open tracepoint and software events, so the parent context will have 3 different perf_event_pmu_contexts. On inheritance, child ctx will insert the perf_event_pmu_context in another order and the warning will trigger. [ mingo: Tidied up the changelog. ]
A vulnerability in the Linux kernel's performance monitoring unit (PMU) context handling has been addressed. The issue arose because the order of PMU context lists could differ between parent and child processes, leading to warnings about unordered PMU contexts. This discrepancy was caused by the timing of when events were added to the PMU list, which varied between parent and child processes. The vulnerability could be triggered by a specific sequence of performance monitoring events, as demonstrated in a provided test case.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2016066c66192a99d9e0ebf433789c490a6785a2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/3e812a70732d84b7873cea61a7f6349b9a9dcbf5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7d582eb6e4e100959ba07083d7563453c8c2a343 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f0c3971405cef6892844016aa710121a02da3a23 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.2, < 6.6.81 >= 6.7, < 6.12.18 >= 6.13, < 6.13.6 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 31, 2025 | Initial Analysis | [email protected] |
| Apr 1, 2025 | New CVE Received | kernel.org |