tick/broadcast: Plug clockevents replacement race
Summary
| CVE | CVE-2026-97925 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:19 UTC |
| Updated | 2026-09-25 11:17:19 UTC |
| 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. |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.088200000 (date 2026-09-27)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 3da55616db2b6b7d9caa3b7ff1e8983224e0ed52 git | Not specified |
| CNA | Linux | Linux | affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818 git | Not specified |
| CNA | Linux | Linux | affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 292b7a8ed84032cfdfc9076a690360f7d3f640d4 git | Not specified |
| CNA | Linux | Linux | affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 113a9796effe3376d2ec5aabcca1fef4fef4cd62 git | Not specified |
| CNA | Linux | Linux | affected 2.6.21 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.21 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/292b7a8ed84032cfdfc9076a690360f7d3f640d4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3525b94b2f258e0b99d1ee5a82a80b51bc1cc818 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3da55616db2b6b7d9caa3b7ff1e8983224e0ed52 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/113a9796effe3376d2ec5aabcca1fef4fef4cd62 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.