CVE-2026-90002 Affecting kernel6.18-debuginfo package, versions <1:6.18.54-121.166.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-KERNEL618DEBUGINFO-21425156
- published22 Oct 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
CVE-2026-90002 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel6.18-debuginfo to version 1:6.18.54-121.166.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3192.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel6.18-debuginfo package and not the kernel6.18-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-90002
- https://git.kernel.org/stable/c/83fd7eca5ab0d3ac3f23bff889175d847e21af06
- https://git.kernel.org/stable/c/9100191e5acb2e5ea2313f436667bb5fce129f47
- https://git.kernel.org/stable/c/cee8f286794df916553d8d445eac5c323ec5b0f8
- https://git.kernel.org/stable/c/177cd8966325f0ffffa3c9381f9e0422019a3973
- https://git.kernel.org/stable/c/29266da8ee1d9be656b1f22460c49538e1930658