CVE-2026-97925: tick/broadcast: Plug clockevents replacement race
Vulnerability summary
CVE-2026-97925 is a vulnerability in linux with no CVSS score yet. EPSS estimates a 0.21% chance of exploitation in the next 30 days, higher than 11.4% of scored vulnerabilities.
No CVSS vector published; no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 24 · Related 19Timeline
- 25-09-2026PublishedVulnerability first disclosed.
- 30-10-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Plug clockevents replacement race 朱恺乾 reported and decoded the following race condition when a broadcast device is replaced: CPUA CPUB __tick_broadcast_oneshot_control() bc = tick_broadcast_device.evtdev; tick_install_broadcast_device(dev) clockevents_exchange_device(cur, dev) shutdown(cur); detach(cur); cur->handler = noop; tick_broadcast_device.evtdev = dev; tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device. If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state. The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations. The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation. That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock. Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.
CVSS metrics
Risk metrics not yet published.
EPSS trend
Probability
0.21%
Chance of exploitation in the next 30 days
Percentile
11%
Versus all other CVEs
30-day change
Increase +0.01 pp
From 0.21% on 21-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Known conditions: not stated in public data.
Ubuntu169 products
- linuxAll versions (No fix recorded) | < 5.15.0-204.214 | < 6.8.0-149.149 | < 7.0.0-42.42
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 5.15.0-1121.128 | < 6.8.0-1069.74 | < 7.0.0-1016.17
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Debian2 products
- linuxAll versions (No fix recorded) | < 6.1.190-1 | < 6.12.111-1 | < 7.2.7-1
- linux-6.12< 6.12.111-1~deb12u1
Linux1 product
- linux≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 9fa1fb4a876e10cc17182ce339625ec4d4b75f20 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < bc988724973b7f50d5dd05637f1e9ef4f009afd5 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 338d6859cd1580617807290f6d7e92b1662d4695 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 757aa9f548c18b96da1d56d11f65be8188a16d59 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 3da55616db2b6b7d9caa3b7ff1e8983224e0ed52 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 292b7a8ed84032cfdfc9076a690360f7d3f640d4 | ≥ f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98, < 113a9796effe3376d2ec5aabcca1fef4fef4cd62 | 2.6.21
3 vendors · 172 products