CVE-2026-97925: Linux kernel · tick/broadcast: Plug clockevents replacement race
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Medium by Threat Radar's AI analysis · 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.
- Patch
- Available – fixed in 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818, 757aa9f548c18b96da1d56d11f65be8188a16d59, 338d6859cd1580617807290f6d7e92b1662d4695 +3
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
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. The patch serializes tick_install_broadcast_device() with tick_broadcast_lock and refactors clockevents_exchange_device() to prevent the race condition. Users should update to a Linux kernel version that includes the fix identified by the provided commit hashes.
Description
A race condition vulnerability in the Linux kernel's tick broadcast device replacement mechanism was identified and fixed. The issue occurs when a broadcast clockevent device is replaced without proper serialization, leading to a potential 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 with a broadcast lock and splitting the device exchange and module reference count drop into two steps.
References
- git.kernel.org/stable/c/338d6859cd1580617807290f6d7e92b1662d4695 (opens in a new tab)
- git.kernel.org/stable/c/757aa9f548c18b96da1d56d11f65be8188a16d59 (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)
- git.kernel.org/stable/c/113a9796effe3376d2ec5aabcca1fef4fef4cd62 (opens in a new tab)