CVE-2026-99173·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: eventfs: Free the eventfs_inode after an rcu grace period too tracefs_d_revalidate() reads ->is_freed of the eventfs_inode that dentry->d_fsdata points to, and ->d_revalidate() is called in rcu pathwalk mode with nothing but rcu_read_lock() held. The dentry itself stays around for such a walker, but tracefs_d_release() drops its reference to the eventfs_inode when the dentry is killed, and release_ei() then frees it after a grace period of eventfs_srcu. An SRCU grace period doesn't wait for rcu_read_lock() sections, so the walker can read an eventfs_inode that is already gone. With a pathwalk held up in tracefs_d_revalidate() while the dentry goes away: BUG: KASAN: slab-use-after-free in tracefs_d_revalidate+0x76/0x90 Read of size 1 at addr ff1100010152d8d0 by task walker/97 Call Trace: <TASK> tracefs_d_revalidate+0x76/0x90 lookup_fast+0x320/0x640 path_lookupat+0x160/0xb00 filename_lookup+0x1f1/0x5b0 vfs_statx+0xd7/0x3b0 vfs_fstatat+0x4d/0x90 __do_sys_newfstatat+0xa0/0x100 do_syscall_64+0x10e/0x5e0 entry_SYSCALL_64_after_hwframe+0x77/0x7f [...] Allocated by task 1: __kmalloc_cache_noprof+0x249/0x560 eventfs_create_dir+0x7a/0x590 event_create_dir+0x2fb/0xcf0 trace_add_event_call+0xbf/0x150 [...] Freed by task 11: kfree+0x1db/0x5b0 srcu_invoke_callbacks+0x3a3/0x620 process_one_work+0x937/0x1810 worker_thread+0x4f1/0xd60 Before commit 8e556432477e ("eventfs: Use SRCU for freeing eventfs_inodes") release_ei() used call_rcu(), which covered the walker, while eventfs_iterate() needs the SRCU grace period. Wait for both and chain call_rcu() from the SRCU callback.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.6.161, 6.12.115, 6.18.59, 7.2.13, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.17% — higher than 6% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-99173 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.17%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version that includes the eventfs SRCU grace period fix. Users should upgrade to kernel 6.6.161, 6.12.115, 6.18.59, 7.2.13, or later depending on their current kernel branch. If you are running a distribution-provided kernel, check your package manager for patched kernel updates rather than manually compiling mainline.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your current kernel version: uname -r
- Compare against fixed versions: kernel 6.6.161+, 6.12.115+, 6.18.59+, or 7.2.13+
- Search system logs for KASAN errors related to tracefs_d_revalidate: sudo grep -i 'tracefs_d_revalidate\|slab-use-after-free' /var/log/kern.log /var/log/syslog 2>/dev/null
- Verify the patch was applied by checking kernel source or comparing installed package version: apt-cache policy linux-image-generic (Ubuntu) or dnf info kernel (RHEL/CentOS)
FAQ
What is CVE-2026-99173?
CVE-2026-99173 is a use-after-free vulnerability in the Linux kernel's eventfs subsystem. When a path walk operation is in progress during dentry revalidation, the eventfs_inode can be freed while still being accessed, leading to memory corruption and potential system instability.
Is CVE-2026-99173 being actively exploited?
No, this vulnerability is not currently listed as actively exploited in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available.
What versions of Kernel are affected by CVE-2026-99173?
Kernel versions prior to 6.6.161, 6.12.115, 6.18.59, 7.2.13, and mainline 7.3 are affected. Specific stable branches should be updated to their respective fixed versions.
How do I check if my server is vulnerable to CVE-2026-99173?
Run 'uname -r' and check if your kernel version is below the fixed versions for your branch. For example, if running 6.6.x, ensure you are on 6.6.161 or later.
Does Defensia detect CVE-2026-99173?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-99173 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/2cd88c498ecff8e22bf4c397b8eb226db70ac343
- https://git.kernel.org/stable/c/4586ef24ce390e8becb9f3e5852d5d3978b01c33
- https://git.kernel.org/stable/c/45fcfd5d9c10e0aa977ed5b9bd445707e01bb107
- https://git.kernel.org/stable/c/5819018dc29fb2ac2fd4865d507f9893c89c0624
- https://git.kernel.org/stable/c/dd2c767814a876be0f16f0b7f98a403dc176f51e
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-99173. Free for 1 server.
Get started free