CVE-2025-68214 is a race condition in the Linux kernel timer subsystem involving timer_shutdown_sync(). The bug occurs when timer_shutdown_sync() clears timer->function to NULL even though the timer is still executing on another CPU. In the described sequence, expire_timers() has already selected the timer as base->running_timer and released the timer base lock before invoking the callback path. While that callback is still in progress, another CPU enters timer_shutdown_sync(), observes shutdown state, and clears the timer function pointer without detaching the timer if it is currently running. If the running callback re-arms the timer via mod_timer(), the timer can remain pending with a NULL callback. On the next expiration, expire_timers() encounters the pending timer and hits WARN_ON_ONCE(!fn). The fix is to clear the timer function pointer only when the timer is actually detached; if the timer is still running, the function pointer must remain intact until the timer completes and can be safely detached.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.