Kernel crash via stale ftrace module reference
Published Jul 10, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel ftrace allows local users to crash the kernel through module teardown followed by kallsyms access. ftrace_release_mod() returns early when ftrace_disable is set, leaving mod_list with a pointer to unloaded module memory that ftrace_mod_get_kallsym() later copies. The demonstrated sequence requires a kprobe tracepoint and a buggy module that disables ftrace before unloading, followed by access to /proc/kallsyms.
Summary
What happened
Use-after-free in Linux kernel ftrace allows local users to crash the kernel through module teardown followed by kallsyms access. ftrace_release_mod() returns early when ftrace_disable is set, leaving mod_list with a pointer to unloaded module memory that ftrace_mod_get_kallsym() later copies. The demonstrated sequence requires a kprobe tracepoint and a buggy module that disables ftrace before unloading, followed by access to /proc/kallsyms.
The record
- CVE
- CVE-2025-38346
- Published
- Jul 10, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.15
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <03a162933c4a03b9f1a84f7d8482903c7e1e11bb
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <6805582abb720681dd1c87ff677f155dcf4e86c9
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <83a692a9792aa86249d68a8ac0b9d55ecdd255fa
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <8690cd3258455bbae64f809e1d3ee0f043661c71
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <8e89c17dc8970c5f71a3a991f5724d4c8de42d8c
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <d064c68781c19f378af1ae741d9132d35d24b2bb
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <f78a786ad9a5443a29eef4dae60cde85b7375129
- Affected versionversion=aba4b5c22cbac296f4081a0476d0c55828f135b4 <f914b52c379c12288b7623bb814d0508dbe7481d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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