CVE-2026-97925: Linux kernel · tick/broadcast: Plug clockevents replacement race
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented that serializes tick_install_broadcast_device() with tick_broadcast_lock to prevent the race condition. Users should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation.
Description
A race condition vulnerability in the Linux kernel's tick broadcast device replacement mechanism has been resolved. The issue occurs when a broadcast clockevent device is replaced without proper serialization, potentially leading to a BUG() in tick_cleanup_dead_cpu() if the original device has a restricted interrupt affinity mask and the last CPU in that mask goes offline. The fix involves serializing the device replacement operations with a lock to prevent concurrent tick broadcast operations from causing inconsistent device states.
References
- ubuntu.com/security/CVE-2026-97925 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97925 (opens in a new tab)
- git.kernel.org/stable/c/113a9796effe3376d2ec5aabcca1fef4fef4cd62 (opens in a new tab)
- git.kernel.org/stable/c/3da55616db2b6b7d9caa3b7ff1e8983224e0ed52 (opens in a new tab)
- git.kernel.org/stable/c/3525b94b2f258e0b99d1ee5a82a80b51bc1cc818 (opens in a new tab)
- git.kernel.org/stable/c/292b7a8ed84032cfdfc9076a690360f7d3f640d4 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-97925 (opens in a new tab)
- git.kernel.org/stable/c/338d6859cd1580617807290f6d7e92b1662d4695 (opens in a new tab)
- git.kernel.org/stable/c/757aa9f548c18b96da1d56d11f65be8188a16d59 (opens in a new tab)