CVE-2025-21889 Details
Description
In the Linux kernel, the following vulnerability has been resolved: perf/core: Add RCU read lock protection to perf_iterate_ctx() The perf_iterate_ctx() function performs RCU list traversal but currently lacks RCU read lock protection. This causes lockdep warnings when running perf probe with unshare(1) under CONFIG_PROVE_RCU_LIST=y: WARNING: suspicious RCU usage kernel/events/core.c:8168 RCU-list traversed in non-reader section!! Call Trace: lockdep_rcu_suspicious ? perf_event_addr_filters_apply perf_iterate_ctx perf_event_exec begin_new_exec ? load_elf_phdrs load_elf_binary ? lock_acquire ? find_held_lock ? bprm_execve bprm_execve do_execveat_common.isra.0 __x64_sys_execve do_syscall_64 entry_SYSCALL_64_after_hwframe This protection was previously present but was removed in commit bd2756811766 ("perf: Rewrite core context handling"). Add back the necessary rcu_read_lock()/rcu_read_unlock() pair around perf_iterate_ctx() call in perf_event_exec(). [ mingo: Use scoped_guard() as suggested by Peter ]
A vulnerability has been identified in the Linux kernel's perf/core component, specifically within the perf_iterate_ctx() function. This function traverses RCU lists but currently lacks the necessary RCU read lock protection. As a result, lockdep warnings are generated when running perf probe with unshare(1) under CONFIG_PROVE_RCU_LIST=y. The absence of proper RCU read lock handling can lead to suspicious RCU usage warnings, indicating that the RCU-list was traversed outside of a designated reader section.
The vulnerability has been addressed by adding the necessary rcu_read_lock() and rcu_read_unlock() calls around the perf_iterate_ctx() invocation in the perf_event_exec() function.
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.
No SSVC data is available for this CVE.
References 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/0fe8813baf4b2e865d3b2c735ce1a15b86002c74 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a2475ccad6120546ea45dbcd6cd1f74dc565ef6b | kernel.org | Patch |
| https://git.kernel.org/stable/c/dd536566dda9a551fc2a2acfab5313a5bb13ed02 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f390c2eea571945f357a2d3b9fcb1c015767132e | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [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
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 29, 2025 | Initial Analysis | [email protected] |
| Mar 27, 2025 | New CVE Received | kernel.org |