Skip to main content
Mallory
MediumVulnerability

CVE-2025-68214: Linux kernel timer shutdown race causing denial of service

Published Dec 16, 2025 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.7Medium · v3.1
EPSS0.14%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-68214CWE-362 · Concurrent Execution using Shared…

CVE-2025-68214 is a race condition in the Linux kernel between timer_shutdown_sync() and timer expiration on another CPU. During shutdown, the kernel can clear a timer's callback pointer while that timer is still executing. If the running callback has rearmed the timer, shutdown initially leaves it attached, creating a pending timer with a NULL callback. If the timer expires again before shutdown detaches it, expire_timers() triggers WARN_ON_ONCE(!fn). This condition can cause kernel instability or denial of service, depending on warning handling and system configuration.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disrupt system availability by triggering a kernel warning during timer expiration. Systems configured to panic on kernel warnings can suffer a kernel panic and service interruption. The vulnerability is assessed as having high availability impact, with no confidentiality or integrity impact; arbitrary code execution and privilege escalation are not established.

Mitigation

If you can’t patch tonight, do this now.

No reliable vulnerability-specific workaround is identified. Restrict untrusted local access while awaiting kernel updates. Where operationally acceptable, avoiding configurations that escalate kernel warnings to panics may reduce the immediate availability impact, but does not eliminate the underlying race.

Remediation

Patch, then assume compromise.

Install the distribution-supported kernel update containing the timer_shutdown_sync() fix, then reboot into the corrected kernel or apply a supported live patch where available. The fix clears the callback pointer only when the timer can actually be detached, preserving it while the timer is running. Identified fixed packages include Echo linux and related packages version 6.1.159-1 or later, and Google Container-Optimized OS sys-kernel/csql-kernel-6_6 and related packages version 18867.294.76 or later. These version thresholds are distribution-specific and are not universal upstream kernel version boundaries.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-68214 exploited in the wild?
As of Nov 5, 2026, Mallory has no reports of CVE-2025-68214 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-68214?
As of Nov 5, 2026, Mallory has found no public exploit for CVE-2025-68214.
Is there a patch for CVE-2025-68214?
Install the distribution-supported kernel update containing the timer_shutdown_sync() fix, then reboot into the corrected kernel or apply a supported live patch where available. The fix clears the callback pointer only when the timer can actually be detached, preserving it while the timer is running.
What products are affected by CVE-2025-68214?
Linux Kernel.
How severe is CVE-2025-68214?
CVE-2025-68214 has a CVSS v3.1 score of 4.7 (Medium) and an EPSS score of 0.14% (3rd percentile) as of Nov 5, 2026.
Activity feed

Recent activity

19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.