CVE-2022-49977 is a flaw in the Linux kernel ftrace subsystem. If ftrace_startup_enable fails after an ftrace operation has been added to ftrace_ops_list, ftrace is disabled but the failed registration is not rolled back. Subsequent unregistration returns early while ftrace is disabled, leaving the dynamically allocated operation on the list after it may be freed. is_ftrace_trampoline can then dereference the stale operation while traversing ftrace_ops_list, causing a kernel NULL-pointer dereference and kernel OOPS.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A NULL-pointer dereference vulnerability in the Linux kernel ftrace subsystem's is_ftrace_trampoline path when ftrace is inactive, affecting Rocky Linux 8 kernel packages.
A NULL-pointer dereference in the Linux kernel ftrace is_ftrace_trampoline path when ftrace is inactive.
NULL-pointer dereference in Linux kernel ftrace's is_ftrace_trampoline when ftrace is unavailable or dead.
A NULL-pointer dereference in the Linux kernel ftrace is_ftrace_trampoline path when ftrace is dead.
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.