data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-74605 in the interactive tracker

CVE-2026-74605

eventfs: Use children field for rcu head and add memory barriers

7.8 EPSS 0.2% AV:L

Published 2026-08-22 (2 months ago) by the Linux kernel CNA. Subsystem fs/tracefs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-74605 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed7.1.9-1Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.9-1Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

When an eventfs inode is freed, it sets ei->is_freed and then uses its ei->list to add it to the srcu link list as the list field is a union with the rcu list head. As the ei->list is used to iterate over an SRCU protected list without taking the eventfs_mutex, there's nothing stopping the iteration over that list to see the ei->rcu instead of the ei->list and it will read a corrupt target. To fix this, change the union of the rcu list head with the children list. On freeing the eventfs inode, set the is_free and execute a smp_wmb() before adding the eventfs inode to the SRCU list. On iteration of the ei->children list, at the start, execute a smp_rmb() and then read the is_freed of the ei to see if the children list is still valid. If is_freed is set, then the ei_child read is not valid and the loop should exit immediately.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/tracefs/event_inode.c
fs/tracefs/internal.h

What this is
TRACINGMAINTAINERS section matched on fs/tracefs/ · linux-kernel@vger.kernel.org · Maintained

Check it on the machine

grep -w CONFIG_TRACING /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian builds this code. Every release with an answer below compiles the affected file into the kernels it ships. The build rule could not be established for 1 release, so nothing is claimed about those.

  • bookworm?
  • trixie, forky, sidy
?
not established - no Makefile entry for the affected file
y
built into the kernel image on every flavour - only a patch removes it

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switch
CONFIG_TRACING

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-08-22 (2 months ago)source
CVSS
7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
local (AV:L)source
EPSS
0.17%, higher than 6.3% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
fs/tracefs

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.86.18.572b80707b9e27
6.87.1.9004f7232e497
6.87.2f0ece16ffca7
6.6.1800
6.7.600

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:LAttack vector, local
The bug is reached only via local syscalls (getdents64/readdir on tracefs eventfs directories through eventfs_iterate); tracefs is a kernel pseudo-filesystem under /sys/kernel/tracing with no network, adjacent-wireless, or physical-device entry path.
AC:LAttack complexity, low
A single multithreaded attacker can loop getdents on events/ or events/kprobes/ while concurrently adding/removing kprobes via kprobe_events writes that call eventfs_remove_dir; the attacker controls both the SRCU list walk and the free path, making the race reliably triggerable.
PR:LPrivileges required, low
Exploitation needs only local tracefs read/write access (getdents plus kprobe_events to create/remove eventfs children); kprobe_events checks only LOCKDOWN_TRACEFS and DAC with no capable(), and tracing-group gid mounts, Android/ChromeOS, and developer systems commonly grant this to unprivileged users.
UI:NUser interaction, none
The attacker performs all concurrent directory reads and dynamic event removals in their own process; no separate victim mount, click, or configuration action is required beyond tracefs already being accessible on the system.
S:UScope, unchanged
The union misuse causes kernel heap/list corruption and use-after-free within the tracing filesystem subsystem on the same host; it does not cross VM, container, IOMMU, or other security boundaries to affect a different authority.
C:HConfidentiality impact, high
During list_for_each_entry_srcu over ei->children, a concurrently freed child repurposes ei->list (union with rcu_head) for SRCU teardown, so the iterator follows corrupt list pointers and dereferences freed or attacker-influenced kernel memory typical of UAF read primitives.
I:HIntegrity impact, high
Corrupt SRCU list traversal over freed eventfs_inode objects is classic kernel UAF memory corruption that can be combined with heap grooming from repeated kprobe create/delete to obtain arbitrary kernel writes and local privilege escalation, not merely a bounded crash.
A:HAvailability impact, high
Following a child's list.next after the list/rcu union is switched during free_ei() readily causes invalid pointer dereferences, kernel oops, or panic; the race can be retriggered at will by alternating getdents with dynamic event teardown.