CVE-2025-22035 Details
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix use-after-free in print_graph_function_flags during tracer switching Kairui reported a UAF issue in print_graph_function_flags() during ftrace stress testing [1]. This issue can be reproduced if puting a 'mdelay(10)' after 'mutex_unlock(&trace_types_lock)' in s_start(), and executing the following script: $ echo function_graph > current_tracer $ cat trace > /dev/null & $ sleep 5 # Ensure the 'cat' reaches the 'mdelay(10)' point $ echo timerlat > current_tracer The root cause lies in the two calls to print_graph_function_flags within print_trace_line during each s_show(): * One through 'iter->trace->print_line()'; * Another through 'event->funcs->trace()', which is hidden in print_trace_fmt() before print_trace_line returns. Tracer switching only updates the former, while the latter continues to use the print_line function of the old tracer, which in the script above is print_graph_function_flags. Moreover, when switching from the 'function_graph' tracer to the 'timerlat' tracer, s_start only calls graph_trace_close of the 'function_graph' tracer to free 'iter->private', but does not set it to NULL. This provides an opportunity for 'event->funcs->trace()' to use an invalid 'iter->private'. To fix this issue, set 'iter->private' to NULL immediately after freeing it in graph_trace_close(), ensuring that an invalid pointer is not passed to other tracers. Additionally, clean up the unnecessary 'iter->private = NULL' during each 'cat trace' when using wakeup and irqsoff tracers. [1] https://lore.kernel.org/all/[email protected]/
A use-after-free vulnerability has been identified in the Linux kernel's tracing functionality, specifically within the 'print_graph_function_flags' during tracer switching. This issue arises because the 'function_graph' tracer's print line function is not properly updated when switching to the 'timerlat' tracer, leading to the use of an invalid pointer. The vulnerability can be reproduced by introducing a delay after unlocking a mutex, switching tracers, and allowing a 'cat' command to reach the delayed point before switching again.
The vulnerability has been fixed in the Linux kernel by ensuring that the private iterator is set to NULL after being freed, preventing the use of an invalid pointer in tracer functions.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 21, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.14.324, < 4.15 >= 4.19.293, < 4.20 >= 5.4.255, < 5.4.292 >= 5.10.193, < 5.10.236 >= 5.15.129, < 5.15.180 >= 6.1.50, < 6.1.134 >= 6.4.13, < 6.6.87 >= 6.7, < 6.12.23 >= 6.13, < 6.13.11 >= 6.14, < 6.14.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 3, 2025 | CVE Modified | CVE |
| Apr 25, 2025 | Initial Analysis | [email protected] |
| Apr 21, 2025 | CVE Modified | CISA-ADP |
| Apr 16, 2025 | New CVE Received | kernel.org |