7.8
HIGH CVSS 3.1
CVE-2025-22035
Linux Kernel: Ftrace Tracing Use-After-Free Vulnerability in print_graph_function_flags
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]/

INFO

Published Date :

April 16, 2025, 3:15 p.m.

Last Modified :

April 25, 2025, 6:43 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-22035 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH 134c704f-9b21-4f2e-91b3-4a467353bcc0
Solution
Update the Linux kernel to fix a use-after-free vulnerability in tracer switching.
  • Update the Linux kernel to the latest version.
  • Apply the provided patch for tracing use-after-free.
  • Ensure iter->private is NULL after freeing.
  • Clean up iter->private during specific tracer switches.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-22035 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-22035 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-22035 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2025-22035 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Apr. 25, 2025

    Action Type Old Value New Value
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.13.11 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.14 up to (excluding) 6.14.2 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.23 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.14.324 up to (excluding) 4.15 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.293 up to (excluding) 4.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.193 up to (excluding) 5.10.236 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.255 up to (excluding) 5.4.292 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.129 up to (excluding) 5.15.180 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.50 up to (excluding) 6.1.134 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.4.13 up to (excluding) 6.6.87
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70 Types: Patch
  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Apr. 21, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    Added CWE CWE-416
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 16, 2025

    Action Type Old Value New Value
    Added 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]/
    Added Reference https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a
    Added Reference https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f
    Added Reference https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb
    Added Reference https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906
    Added Reference https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b
    Added Reference https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e
    Added Reference https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a
    Added Reference https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813
    Added Reference https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 7.8
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact