Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2025-21895— perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于PMU列表顺序问题导致关于无序pmu_ctx_list的警告。

AI Predicted 3.3 Difficulty: Hard EPSS 0.14% · P3

Possible ATT&CK Techniques 1 AI

T1057 · Process Discovery

Affected Version Matrix 10

VendorProduct Version RangeStatus
Linux Linux bd27568117664b8b3e259721393df420ed51f57b< f0c3971405cef6892844016aa710121a02da3a23 affected
bd27568117664b8b3e259721393df420ed51f57b< 7d582eb6e4e100959ba07083d7563453c8c2a343 affected
bd27568117664b8b3e259721393df420ed51f57b< 3e812a70732d84b7873cea61a7f6349b9a9dcbf5 affected
bd27568117664b8b3e259721393df420ed51f57b< 2016066c66192a99d9e0ebf433789c490a6785a2 affected
6.2 affected
< 6.2 unaffected
6.6.81≤ 6.6.* unaffected
6.12.18≤ 6.12.* unaffected
… +2 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2025-21895

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list
Source: CVE Program / CVE List V5
Vulnerability 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. ]
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于PMU列表顺序问题导致关于无序pmu_ctx_list的警告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux bd27568117664b8b3e259721393df420ed51f57b ~ f0c3971405cef6892844016aa710121a02da3a23 -
Linux Linux 6.2 -

II. Public POCs for CVE-2025-21895

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-21895

请登录查看更多情报信息。

Patches & Fixes for CVE-2025-21895 (3)

Same Patch Batch · Linux · 2025-04-01 · 93 CVEs total

CVE-2025-21927 9.8 CRITICAL nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()
CVE-2025-21954 9.8 CRITICAL netmem: prevent TX of unreadable skbs
CVE-2025-21969 8.8 HIGH Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd
CVE-2025-21955 8.8 HIGH ksmbd: prevent connection release during oplock break notification
CVE-2025-21972 8.8 HIGH net: mctp: unshare packets when reassembling
CVE-2025-21946 8.8 HIGH ksmbd: fix out-of-bounds in parse_sec_desc()
CVE-2025-21945 8.8 HIGH ksmbd: fix use-after-free in smb2_lock
CVE-2025-21967 8.8 HIGH ksmbd: fix use-after-free in ksmbd_free_work_struct
CVE-2025-21947 8.1 HIGH ksmbd: fix type confusion via race condition when using ipc_msg_send_request
CVE-2025-21923 7.8 HIGH HID: hid-steam: Fix use-after-free when detaching device
CVE-2025-21934 7.8 HIGH rapidio: fix an API misues when rio_add_net() fails
CVE-2025-21949 7.8 HIGH LoongArch: Set hugetlb mmap base address aligned with pmd size
CVE-2025-21939 7.8 HIGH drm/xe/hmm: Don't dereference struct page pointers without notifier lock
CVE-2025-21914 7.8 HIGH slimbus: messaging: Free transaction ID in delayed interrupt scenario
CVE-2025-21924 7.8 HIGH net: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an e
CVE-2025-21958 7.8 HIGH Revert "openvswitch: switch to per-action label counting in conntrack"
CVE-2025-21965 7.8 HIGH sched_ext: Validate prev_cpu in scx_bpf_select_cpu_dfl()
CVE-2025-21926 7.8 HIGH net: gso: fix ownership in __udp_gso_segment
CVE-2025-21919 7.8 HIGH sched/fair: Fix potential memory corruption in child_cfs_rq_on_list
CVE-2025-21985 7.8 HIGH drm/amd/display: Fix out-of-bound accesses

Showing top 20 of 93 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2025-21895

No comments yet


Leave a comment