CVE-2025-22035

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2025-22035
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/

7.8 /10

CVSS v3 : HIGH

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a Patch
https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f Patch
https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb Patch
https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906 Patch
https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b Patch
https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e Patch
https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a Patch
https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813 Patch
https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

25 Apr 2025, 18:43

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a - () https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a - Patch
References () https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f - () https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f - Patch
References () https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb - () https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb - Patch
References () https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906 - () https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906 - Patch
References () https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b - () https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b - Patch
References () https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e - () https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e - Patch
References () https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a - () https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a - Patch
References () https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813 - () https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813 - Patch
References () https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70 - () https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70 - Patch
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

21 Apr 2025, 15:15

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 7.8
CWE CWE-416
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tracing: Fix use-after-free en print_graph_function_flags durante el cambio de tracer Kairui informó de un problema de UAF en print_graph_function_flags() durante las pruebas de estrés de ftrace [1]. Este problema se puede reproducir si se pone un 'mdelay(10)' después de 'mutex_unlock(&trace_types_lock)' en s_start() y se ejecuta el siguiente script: $ echo function_graph > current_tracer $ cat trace > /dev/null & $ sleep 5 # Asegurarse de que 'cat' alcance el punto 'mdelay(10)' $ echo timerlat > current_tracer La causa raíz se encuentra en las dos llamadas a print_graph_function_flags dentro de print_trace_line durante cada s_show(): * Una a través de 'iter->trace->print_line()'; * Otra función mediante 'event->funcs->trace()', que está oculta en print_trace_fmt() antes del retorno de print_trace_line. Al cambiar de trazador, solo se actualiza el primero, mientras que el segundo continúa usando la función print_line del trazador anterior, que en el script anterior es print_graph_function_flags. Además, al cambiar del trazador 'function_graph' al trazador 'timerlat', s_start solo llama a graph_trace_close del trazador 'function_graph' para liberar 'iter->private', pero no lo establece en NULL. Esto permite que 'event->funcs->trace()' use un 'iter->private' no válido. Para solucionar este problema, establezca 'iter->private' en NULL inmediatamente después de liberarlo en graph_trace_close(), lo que garantiza que no se pase un puntero no válido a otros trazadores. Además, limpie el 'iter->private = NULL' innecesario durante cada 'cat trace' al usar los trazadores wakeup e irqsoff. [1] https://lore.kernel.org/all/20231112150030.84609-1-ryncsn@gmail.com/

16 Apr 2025, 15:15

Type Values Removed Values Added
New CVE
Information

Published : 2025-04-16 15:15

Updated : 2025-04-25 18:43

NVD link : CVE-2025-22035

Mitre link : CVE-2025-22035

CVE.ORG link : CVE-2025-22035

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-416

Use After Free