EUVD-2026-80610
GHSA-hxw4-9m57-prf4
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local tracefs access gated by root (PR:H, AV:L); tight open-vs-rmdir race (AC:H); UAF yields a kernel crash (A:H) with slab corruption (I:L) and no disclosure (C:N).
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
5DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
ftrace: Take trace_array reference before accessing its ftrace_ops
The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.
Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.
This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.
AnalysisAI
A race-condition use-after-free in the Linux kernel ftrace subsystem lets a local attacker with root or CAP_SYS_ADMIN privileges crash the kernel by opening a per-instance set_ftrace_filter or set_ftrace_notrace file at the moment another thread removes (rmdir) that same trace instance, causing the freed ftrace_ops structure referenced from inode->private to be dereferenced before a trace_array reference is taken. Affected kernels are those built with ftrace/CONFIG_FUNCTION_TRACER in the range introduced around Linux 3.15 through before the fixes released in 6.18.52, 7.2.5, and 7.3-rc2; only per-instance tracing files are exposed, since the top-level instance uses global_ops and is unaffected. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires local access with privileges to manage kernel function tracing: a mounted tracefs (typically /sys/kernel/tracing) and the ability to create/remove trace instance directories, which needs root/CAP_SYS_ADMIN. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a local, race-condition use-after-free in the Linux kernel ftrace subsystem, not a remotely exploitable flaw. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade to Linux 6.18.52, 7.2.5, or 7.3-rc2, which contain the upstream fix commits 83fd7eca5ab0d3ac3f23bff889175d847e21af06 (https://git.kernel.org/stable/c/83fd7eca5ab0d3ac3f23bff889175d847e21af06), cee8f286794df916553d8d445eac5c323ec5b0f8 (https://git.kernel.org/stable/c/cee8f286794df916553d8d445eac5c323ec5b0f8), and 9100191e5acb2e5ea2313f436667bb5fce129f47 (https://git.kernel.org/stable/c/9100191e5acb2e5ea2313f436667bb5fce129f47); details also appear in the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-90002. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Linux hosts and confirm which are running kernels built with CONFIG_FUNCTION_TRACER in the affected range (introduced around Linux 3.15 through versions before 6.18.52, 7.2.5, and 7.3-rc2), prioritizing multi-tenant and production systems; restrict root and CAP_SYS_ADMIN grants to the minimum personnel strictly required, and monitor for repeated ftrace per-instance file operations or trace instance rmdir activity near set_ftrace_filter/set_ftrace_notrace access as a possible crash attempt. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today