LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46106: eventfs: Hold eventfs_mutex and SRCU when remount walks events

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel tracing filesystem race. During tracefs remounts, kernel code could walk eventfs data without the required locking, so concurrent tracing-event changes could touch deleted or reclaimed kernel objects. The supplied record does not provide CVSS, business impact, or confirmed exploitation.

Executive priority

Prioritize normal kernel patch management, with higher urgency for systems using kernel tracing or allowing administrative tracing access. Current evidence does not support emergency response, but severity is not yet quantified.

Technical view

eventfs_set_attrs() recursively walked eventfs children during tracefs_apply_options() while only under regular RCU. The CVE says this races with list_del_rcu(), SRCU-based freeing of eventfs_inodes, and writes protected by eventfs_mutex. The fix adds eventfs remount lock/unlock coverage using eventfs_mutex and eventfs_srcu.

Likely exposure

Exposure is limited to Linux kernels in the affected version ranges or commits listed in the CVE record. The trigger involves tracefs remount behavior and concurrent eventfs tracing changes. The source bundle does not state whether unprivileged users can trigger it on typical systems.

Exploitation context

The CVE record includes a reproducer pattern, but no KEV listing and no cited source confirms active exploitation. Treat this as a kernel stability and memory-safety issue until vendor severity and distribution advisories clarify impact.

Researcher notes

Key uncertainty is impact: the record describes LIST_POISON dereference, SRCU lifetime mismatch, and attribute write races, but not exploitability beyond the race. Avoid assuming privilege level, remote reachability, or code execution from the supplied sources alone.

Mitigation direction

  • Check whether deployed kernels match the affected versions in the CVE record.
  • Apply vendor kernel updates that include the referenced stable commits.
  • Monitor Linux distribution advisories for severity, backports, and operational guidance.
  • Restrict access to kernel tracing interfaces according to existing hardening policy.

Validation and detection

  • Inventory kernel versions across Linux hosts and appliances.
  • Confirm whether tracefs is mounted and used on exposed systems.
  • Verify patched kernels include the eventfs remount locking changes.
  • Review crash logs for tracefs or eventfs-related kernel faults.
Prepared
Confidence
medium
Sources
7

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-46106 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7ec535ed8724d18ae4e714d2277a5b89450659d2, 340f0c7067a95281ad13734f8225f49c6cf52067, 340f0c7067a95281ad13734f8225f49c6cf52067, 340f0c7067a95281ad13734f8225f49c6cf52067, 340f0c7067a95281ad13734f8225f49c6cf52067, 99b86d85f7c73d676c50e8c35748f94dd41389da, 6.6.35, 6.9.6unaffected
LinuxLinux6.10, 0, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.