CVE-2026-97925

published 25 Sep 2026 · updated 16 Nov 2026

tick/broadcast: Plug clockevents replacement race

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 113a9796effe3376d2ec5aabcca1fef4fef4cd62, Kernel 292b7a8ed84032cfdfc9076a690360f7d3f640d4, Kernel 338d6859cd1580617807290f6d7e92b1662d4695 and 5 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.21, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <113a9796effe3376d2ec5aabcca1fef4fef4cd62, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <292b7a8ed84032cfdfc9076a690360f7d3f640d4, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <338d6859cd1580617807290f6d7e92b1662d4695, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <3525b94b2f258e0b99d1ee5a82a80b51bc1cc818, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <3da55616db2b6b7d9caa3b7ff1e8983224e0ed52, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <757aa9f548c18b96da1d56d11f65be8188a16d59, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <9fa1fb4a876e10cc17182ce339625ec4d4b75f20, >=f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <bc988724973b7f50d5dd05637f1e9ef4f009afd5113a9796effe3376d2ec5aabcca1fef4fef4cd62, 292b7a8ed84032cfdfc9076a690360f7d3f640d4, 338d6859cd1580617807290f6d7e92b1662d4695, 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818, 3da55616db2b6b7d9caa3b7ff1e8983224e0ed52, 757aa9f548c18b96da1d56d11f65be8188a16d59, 9fa1fb4a876e10cc17182ce339625ec4d4b75f20, bc988724973b7f50d5dd05637f1e9ef4f009afd5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97925 severity on Zeptric[![CVE-2026-97925](https://zeptric.io/badge/cve/CVE-2026-97925.svg)](https://zeptric.io/cve/CVE-2026-97925)