CVE-2025-22035tracing: Fix use-after-free in print_graph_function_flags during tracer switching
- 7.8HighCVSS base score
- 0.31%Exploitation in 30 daysEPSS · top 76% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]/
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 16 months later
· 16 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.31% · top 76% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 05319d707732c728eb721ac616a50e7978eb499a – < 42561fe62c3628ea3bc9623f64f047605e98857f
- affected b8205dfed68183dc1470e83863c5ded6d7fa30a9 – < de7b309139f862a44379ecd96e93c9133c69f813
- affected ce6e2b14bc094866d9173db6935da2d752f06d8b – < 81a85b12132c8ffe98f5ddbdc185481790aeaa1b
- affected 2cb0c037c927db4ec928cc927488e52aa359786e – < a2cce54c1748216535dda02e185d07a084be837e
- affected eecb91b9f98d6427d4af5fdb8f108f52572a39e7 – < 099ef3385800828b74933a96c117574637c3fb3a
- affected eecb91b9f98d6427d4af5fdb8f108f52572a39e7 – < c85efe6e13743cac6ba4ccf144cb91f44c86231a
- affected eecb91b9f98d6427d4af5fdb8f108f52572a39e7 – < f14752d66056d0c7bffe5092130409417d3baa70
- affected eecb91b9f98d6427d4af5fdb8f108f52572a39e7 – < 70be951bc01e4a0e10d443f3510bb17426f257fb
- affected eecb91b9f98d6427d4af5fdb8f108f52572a39e7 – < 7f81f27b1093e4895e87b74143c59c055c3b1906
- affected d6b35c9a8d51032ed9890431da3ae39fe76c1ae3
- affected 5d433eda76b66ab271f5924b26ddfec063eeb454
- affected 2242640e9bd94e706acf75c60a2ab1d0e150e0fb
- affected 5.4.255 – < 5.4.292
- affected 5.10.193 – < 5.10.236
- affected 5.15.129 – < 5.15.180
- affected 6.1.50 – < 6.1.134
- affected 4.14.324 – < 4.15
- affected 4.19.293 – < 4.20
- affected 6.4.13 – < 6.5
- affected 6.5
- unaffected < 6.5
- unaffected 5.4.292 – ≤ 5.4.*
- unaffected 5.10.236 – ≤ 5.10.*
- unaffected 5.15.180 – ≤ 5.15.*
- unaffected 6.1.134 – ≤ 6.1.*
- unaffected 6.6.87 – ≤ 6.6.*
- unaffected 6.12.23 – ≤ 6.12.*
- unaffected 6.13.11 – ≤ 6.13.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References11
- https://git.kernel.org/stable/c/42561fe62c3628ea3bc9623f64f047605e98857f (opens in a new tab)
- https://git.kernel.org/stable/c/de7b309139f862a44379ecd96e93c9133c69f813 (opens in a new tab)
- https://git.kernel.org/stable/c/81a85b12132c8ffe98f5ddbdc185481790aeaa1b (opens in a new tab)
- https://git.kernel.org/stable/c/a2cce54c1748216535dda02e185d07a084be837e (opens in a new tab)
- https://git.kernel.org/stable/c/099ef3385800828b74933a96c117574637c3fb3a (opens in a new tab)
- https://git.kernel.org/stable/c/c85efe6e13743cac6ba4ccf144cb91f44c86231a (opens in a new tab)
- https://git.kernel.org/stable/c/f14752d66056d0c7bffe5092130409417d3baa70 (opens in a new tab)
- https://git.kernel.org/stable/c/70be951bc01e4a0e10d443f3510bb17426f257fb (opens in a new tab)
- https://git.kernel.org/stable/c/7f81f27b1093e4895e87b74143c59c055c3b1906 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11251 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-22035)Record last updated .