CVE-2025-38346 is a use-after-free vulnerability in the Linux kernel ftrace subsystem. If a faulty module causes ftrace to set ftrace_disable, ftrace_release_mod() returns without releasing the module’s ftrace mapping during module removal. The stale mapping remains on the ftrace module list after the module memory has been freed. A subsequent lookup through /proc/kallsyms invokes ftrace_mod_get_kallsym(), which dereferences the freed module reference while copying the module name.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ftrace use-after-free vulnerability. If ftrace is disabled following an anomaly, ftrace_release_mod() can fail to release module state; subsequently removing that module and reading /proc/kallsyms may dereference freed module memory.
A high-impact local vulnerability affecting Unity Linux systems. Successful exploitation requires local access and low privileges, requires no user interaction, and can result in complete compromise of confidentiality, integrity, and availability.
Linux kernel ftrace use-after-free vulnerability when looking up kallsym after ftrace is disabled.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.