VulnerabilityPublished 25 Sep 2026Updated 30 Oct 2026

CVE-2026-97925: Linux kernel · tick/broadcast: Plug clockevents replacement race

Source GCVE Database

Compare

Authoritative record:CVE-2026-97925· Medium

Not known to be exploited · fixed in bc988724973b7f50d5dd05637f1e9ef4f009afd5 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 17:20 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in bc988724973b7f50d5dd05637f1e9ef4f009afd5, 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818, 757aa9f548c18b96da1d56d11f65be8188a16d59 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-frpq-r7pw-xq84

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < bc988724973b7f50d5dd05637f1e9ef4f009afd5	Fixed in bc988724973b7f50d5dd05637f1e9ef4f009afd5
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818	Fixed in 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 757aa9f548c18b96da1d56d11f65be8188a16d59	Fixed in 757aa9f548c18b96da1d56d11f65be8188a16d59
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 338d6859cd1580617807290f6d7e92b1662d4695	Fixed in 338d6859cd1580617807290f6d7e92b1662d4695
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 292b7a8ed84032cfdfc9076a690360f7d3f640d4	Fixed in 292b7a8ed84032cfdfc9076a690360f7d3f640d4
LinuxLinux	Affected ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 113a9796effe3376d2ec5aabcca1fef4fef4cd62	Fixed in 113a9796effe3376d2ec5aabcca1fef4fef4cd62

AI-suggested

A fix is available that serializes tick_install_broadcast_device() with tick_broadcast_lock and restructures clockevents_exchange_device() to safely handle device exchange and module reference counting. Users should apply the official Linux kernel patch that addresses this race condition to prevent kernel crashes. Since this is a kernel-level issue, updating to a fixed kernel version is the recommended remediation.

Description

CVE-2026-97925 is a race condition vulnerability in the Linux kernel's tick broadcast device replacement code. It occurs when a broadcast clockevent device is replaced without proper serialization, potentially leading to a BUG() triggered by a clockevent device not being in a detached state when a CPU goes offline. The issue arises because tick_install_broadcast_device() is not serialized against concurrent tick broadcast operations, causing a race during device exchange and shutdown.

References

Community reviews

Loading reviews…