CVE-2026-46106 Details
Description
In the Linux kernel, the following vulnerability has been resolved: eventfs: Hold eventfs_mutex and SRCU when remount walks events Commit 340f0c7067a9 ("eventfs: Update all the eventfs_inodes from the events descriptor") had eventfs_set_attrs() recurse through ei->children on remount. The walk only holds the rcu_read_lock() taken by tracefs_apply_options() over tracefs_inodes, which is wrong: - list_for_each_entry over ei->children races with the list_del_rcu() in eventfs_remove_rec() -- LIST_POISON1 deref, same shape as d2603279c7d6. - eventfs_inodes are freed via call_srcu(&eventfs_srcu, ...). rcu_read_lock() does not extend an SRCU grace period, so ti->private can be reclaimed under the walk. - The writes to ei->attr race with eventfs_set_attr(), which holds eventfs_mutex. Reproducer: while :; do mount -o remount,uid=$((RANDOM%1000)) /sys/kernel/tracing; done & while :; do echo "p:kp submit_bio" > /sys/kernel/tracing/kprobe_events echo > /sys/kernel/tracing/kprobe_events done Wrap the events portion of tracefs_apply_options() in eventfs_remount_lock()/_unlock() that take eventfs_mutex and srcu_read_lock(&eventfs_srcu). eventfs_set_attrs() doesn't sleep so the nested rcu_read_lock() is fine; lockdep_assert_held() pins the contract. Comment in tracefs_drop_inode() said "RCU cycle" -- it is SRCU.
A vulnerability has been identified in the Linux kernel's eventfs implementation, specifically in how it handles remount operations. The issue arises because the eventfs_set_attrs function can recursively traverse eventfs inodes during a remount, leading to a race condition. This remount process only maintains a read lock over tracefs inodes, allowing for potential data corruption. The vulnerability can be exploited by concurrently remounting the eventfs filesystem while manipulating kprobe events, creating a race that could be exploited to cause a denial of service or memory corruption.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version.
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/07004a8c4b572171934390148ee48c4175c77eed | kernel.org | Patch |
| https://git.kernel.org/stable/c/44e64d8a432837308f4dda3ffe819f1ec092a0ba | kernel.org | Patch |
| https://git.kernel.org/stable/c/52b109f1b875b912d4ab2c5fdd8c322d47119d9b | kernel.org | Patch |
| https://git.kernel.org/stable/c/ae9cd0b46b1890040006a2fc5e905c5d6053fd02 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ed2ad73bcb0a7a6cc934097d4853b6d5124c317e | 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.6.35, < 6.6.140 >= 6.9.6, < 6.12.88 >= 6.13, < 6.18.30 >= 6.19, < 7.0.7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 25, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 28, 2026 | New CVE Received | kernel.org |