Local denial of service via unyielding ftrace loop
Published May 20, 2025 · Updated May 11, 2026
Denial of service in affected Linux kernel branches from 4.11 allows local users to trigger a soft lockup via the ftrace graph filter. The ftrace_graph_set_hash() loop in kernel/trace/ftrace.c scans every traceable function without a scheduling point when processing set_graph_function input. Local access with permission to write the tracefs function-graph controls and a large traceable-function set are required; the watchdog event interrupts system responsiveness.
Summary
What happened
Denial of service in affected Linux kernel branches from 4.11 allows local users to trigger a soft lockup via the ftrace graph filter. The ftrace_graph_set_hash() loop in kernel/trace/ftrace.c scans every traceable function without a scheduling point when processing set_graph_function input. Local access with permission to write the tracefs function-graph controls and a large traceable-function set are required; the watchdog event interrupts system responsiveness.
The record
- CVE
- CVE-2025-37940
- Published
- May 20, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.11
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <1fce9574b9d515bcb8a75379a8053e18602424e3
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <42ea22e754ba4f2b86f8760ca27f6f71da2d982c
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <4429535acab750d963fdc3dfcc9e0eee42f4d599
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <5d336ac215e5c76e43ef4bca9ba699835e53e2fd
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <618655d54c5f8af5d57b77491d08c0f0ff77d114
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <72be43ff061a889c6ee648a330a42486cafa15a6
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <8dd7d7280357596ba63dfdb4c1725d9dd24bd42a
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <dd38803c9088b848c6b56f4f6d7efc4497bfde61
- Affected versionversion=b9b0c831bed2682c2e3e9f5420fb6985549ef020 <e5b4ae6f01d4a510d5725eca7254519a1093920d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo