Linux Kernel up to 6.14.1 tracing print_graph_function_flags use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.14.1. Affected by this vulnerability is the function print_graph_function_flags of the component tracing. Performing a manipulation results in use after free. This vulnerability is known as CVE-2025-22035. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.14.1. This affects the function print_graph_function_flags of the component tracing. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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]/

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-22035 since 12/29/2024. The exploitability is told to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/15/2026).

The vulnerability scanner Nessus provides a plugin with the ID 234884 (Debian dsa-5907 : affs-modules-6.1.0-33-4kc-malta-di - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.292, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2 or 6.15-rc1 eliminates this vulnerability. Applying the patch 42561fe62c3628ea3bc9623f64f047605e98857f/de7b309139f862a44379ecd96e93c9133c69f813/81a85b12132c8ffe98f5ddbdc185481790aeaa1b/a2cce54c1748216535dda02e185d07a084be837e/099ef3385800828b74933a96c117574637c3fb3a/c85efe6e13743cac6ba4ccf144cb91f44c86231a/f14752d66056d0c7bffe5092130409417d3baa70/70be951bc01e4a0e10d443f3510bb17426f257fb/7f81f27b1093e4895e87b74143c59c055c3b1906 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (234884) and CERT Bund (WID-SEC-2025-0844). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel
  • Dell Avamar
  • SolarWinds Security Event Manager
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • IBM QRadar SIEM

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 234884
Nessus Name: Debian dsa-5907 : affs-modules-6.1.0-33-4kc-malta-di - security update

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 5.4.292/5.10.236/5.15.180/6.1.134/6.6.87/6.12.23/6.13.11/6.14.2/6.15-rc1
Patch: 42561fe62c3628ea3bc9623f64f047605e98857f/de7b309139f862a44379ecd96e93c9133c69f813/81a85b12132c8ffe98f5ddbdc185481790aeaa1b/a2cce54c1748216535dda02e185d07a084be837e/099ef3385800828b74933a96c117574637c3fb3a/c85efe6e13743cac6ba4ccf144cb91f44c86231a/f14752d66056d0c7bffe5092130409417d3baa70/70be951bc01e4a0e10d443f3510bb17426f257fb/7f81f27b1093e4895e87b74143c59c055c3b1906

Timelineinfo

12/29/2024 🔍
04/16/2025 +107 days 🔍
04/16/2025 +0 days 🔍
02/15/2026 +305 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-22035 (🔍)
GCVE (CVE): GCVE-0-2025-22035
GCVE (VulDB): GCVE-100-305085
CERT Bund: WID-SEC-2025-0844 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/16/2025 17:13
Updated: 02/15/2026 01:31
Changes: 04/16/2025 17:13 (59), 04/28/2025 05:29 (2), 07/14/2025 23:24 (7), 10/09/2025 00:24 (1), 02/15/2026 01:31 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!