CVE-2025-22035

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/20231112150030.84609-1-ryncsn@gmail.com/

Gravité et risque d'exploitation

CVE-2025-22035 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.30 %, ce qui la place devant 21.4 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 5d433eda76b66ab271f5924b26ddfec063eeb454, <=6.1.*, <c85efe6e13743cac6ba4ccf144cb91f44c86231a, <=6.12.*, ce6e2b14bc094866d9173db6935da2d752f06d8b, <a2cce54c1748216535dda02e185d07a084be837e, <=6.14.*, 5.15.180, <6.5, <6.1.134, 0, 5.10.193, 2cb0c037c927db4ec928cc927488e52aa359786e, 6.14.2, <de7b309139f862a44379ecd96e93c9133c69f813, 6.1.134, d6b35c9a8d51032ed9890431da3ae39fe76c1ae3, 4.14.324, <4.20, 6.5, <5.10.236, <81a85b12132c8ffe98f5ddbdc185481790aeaa1b, eecb91b9f98d6427d4af5fdb8f108f52572a39e7, <=5.10.*, 6.6.87, <=6.6.*, 6.13.11, 6.12.23, <=5.4.*, 5.4.255, <5.15.180, 4.19.293, <5.4.292, 6.4.13, 6.15, <f14752d66056d0c7bffe5092130409417d3baa70, <70be951bc01e4a0e10d443f3510bb17426f257fb, b8205dfed68183dc1470e83863c5ded6d7fa30a9, 5.10.236, <42561fe62c3628ea3bc9623f64f047605e98857f, <=*, 05319d707732c728eb721ac616a50e7978eb499a, <099ef3385800828b74933a96c117574637c3fb3a, <=5.15.*, 2242640e9bd94e706acf75c60a2ab1d0e150e0fb, <4.15, 5.4.292, 6.1.50, <=6.13.*, <7f81f27b1093e4895e87b74143c59c055c3b1906, 5.15.129) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• 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