CVE-2025-22035
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
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/20231112150030.84609-1-ryncsn@gmail.com/
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 05319d707732c728eb721ac616a50e7978eb499a < 42561fe62c3628ea3bc9623f64f047605e98857f | affected |
| Linux | Linux | b8205dfed68183dc1470e83863c5ded6d7fa30a9 < de7b309139f862a44379ecd96e93c9133c69f813 | affected |
| Linux | Linux | ce6e2b14bc094866d9173db6935da2d752f06d8b < 81a85b12132c8ffe98f5ddbdc185481790aeaa1b | affected |
| Linux | Linux | 2cb0c037c927db4ec928cc927488e52aa359786e < a2cce54c1748216535dda02e185d07a084be837e | affected |
| Linux | Linux | eecb91b9f98d6427d4af5fdb8f108f52572a39e7 < 099ef3385800828b74933a96c117574637c3fb3a | affected |
| Linux | Linux | eecb91b9f98d6427d4af5fdb8f108f52572a39e7 < c85efe6e13743cac6ba4ccf144cb91f44c86231a | affected |
| Linux | Linux | eecb91b9f98d6427d4af5fdb8f108f52572a39e7 < f14752d66056d0c7bffe5092130409417d3baa70 | affected |
| Linux | Linux | eecb91b9f98d6427d4af5fdb8f108f52572a39e7 < 70be951bc01e4a0e10d443f3510bb17426f257fb | affected |
| Linux | Linux | eecb91b9f98d6427d4af5fdb8f108f52572a39e7 < 7f81f27b1093e4895e87b74143c59c055c3b1906 | affected |
| Linux | Linux | d6b35c9a8d51032ed9890431da3ae39fe76c1ae3 | affected |
| Linux | Linux | 5d433eda76b66ab271f5924b26ddfec063eeb454 | affected |
| Linux | Linux | 2242640e9bd94e706acf75c60a2ab1d0e150e0fb | affected |
| Linux | Linux | 5.4.255 < 5.4.292 | affected |
| Linux | Linux | 5.10.193 < 5.10.236 | affected |
| Linux | Linux | 5.15.129 < 5.15.180 | affected |
| Linux | Linux | 6.1.50 < 6.1.134 | affected |
| Linux | Linux | 4.14.324 < 4.15 | affected |
| Linux | Linux | 4.19.293 < 4.20 | affected |
| Linux | Linux | 6.4.13 < 6.5 | affected |
| Linux | Linux | 6.5 | affected |
| Linux | Linux | 0 < 6.5 | unaffected |
| Linux | Linux | 5.4.292 <= 5.4.* | unaffected |
| Linux | Linux | 5.10.236 <= 5.10.* | unaffected |
| Linux | Linux | 5.15.180 <= 5.15.* | unaffected |
| Linux | Linux | 6.1.134 <= 6.1.* | unaffected |
| Linux | Linux | 6.6.87 <= 6.6.* | unaffected |
| Linux | Linux | 6.12.23 <= 6.12.* | unaffected |
| Linux | Linux | 6.13.11 <= 6.13.* | unaffected |
| Linux | Linux | 6.14.2 <= 6.14.* | unaffected |
| Linux | Linux | 6.15 <= * | unaffected |
Weaknesses
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: no
- Technical Impact: total
CVE Program Container
Additional References
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
References
- https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f
- https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813
- https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b
- https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e
- https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a
- https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a
- https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70
- https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb
- https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.