Skip to main content

Linux Kernel EUVDEUVD-2026-80621

| CVE-2026-90013 HIGH
2026-09-16 Linux GHSA-gwf9-fcmv-qx77
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
4.7 MEDIUM

Local tracefs access is root-gated (PR:H) and the flaw is an open-vs-rmdir race (AC:H); outcome is a UAF crash (A:H, minor memory-integrity I:L, no disclosure C:N).

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
4.0 AV:L/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Sep 16, 2026 - 16:27 vuln.today
CVSS changed
Sep 16, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Sep 16, 2026 - 11:03 EUVD
CVE Published
Sep 16, 2026 - 10:33 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 16, 2026 - 10:33 cve.org
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

tracing: Take trace_array reference when opening options file

The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by one task and another task removes the instance that the option is for. Because it doesn't take a reference upon opening, it will not stop the removal which will free the options descriptor that is being used.

As the options are somewhat dynamic in their creation at boot up, each file represents a flag in the trace_array. The trace_array has an array of indexes to represent each of these flags that is stored in the trace_flags_index array. The address of the index array element is used to pass to the inode->i_private pointer. Then that element is read which holds the index (which represents the flag) and then the index is used to calculate the trace_array descriptor from its trace_flags_index array.

One issue is that the index element can not be referenced until the trace_array's reference is taken. To handle this, create a new helper function called: trace_array_options_get() that will iterate all the existing trace_arrays in the ftrace_trace_arrays list (under the trace_types_lock), and compare the passed in address of the index element with the entire array of the trace_array's trace_flags_index array. If it matches, then up the corresponding trace_array's reference and return.

AnalysisAI

A local use-after-free race in the Linux kernel's ftrace/tracing subsystem allows a task that has opened one of the per-instance options files to crash the kernel when a second task concurrently removes the tracing instance that option belongs to. Only systems with ftrace/tracing instances enabled and with access to the tracing filesystem (tracefs/debugfs, normally root- or CAP_SYS_ADMIN-gated) are affected; the open path never took a trace_array reference, so instance removal frees the options descriptor that the first task is still using. …

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

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires local access to the kernel tracing filesystem (tracefs / debugfs, normally /sys/kernel/tracing) which is root/CAP_SYS_ADMIN-gated on default configurations, plus the ability to create and remove tracing instances. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a locally-triggered use-after-free race in the Linux kernel ftrace/tracing subsystem, and the vendor CVSS of 7.8 (AV:L/AC:L/PR:L/C:H/I:H/A:H) overstates real-world risk. … 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 7.3-rc2 (mainline), 7.2.5, or 6.18.52, which contain the fix that adds trace_array_options_get() and takes the trace_array reference on open of the options files (stable commits d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73, and 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5; see https://nvd.nist.gov/vuln/detail/CVE-2026-90013); distribution kernels should be updated to the vendor build that backports these commits. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory Linux servers, VM hosts and container nodes running kernels with ftrace/tracing instances enabled and confirm that tracefs/debugfs access is restricted to root or CAP_SYS_ADMIN; as an interim step, remove or disable unnecessary tracing instances and unmount tracefs where operationally feasible. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-80621 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy