CVE-2026-97925

CVE CVE-2026-97925EUVD EUVD-2026-86779Published 2026-09-25T10:22:43.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.3-rc3; patch: 6.12.111; patch: 6.18.53; 2.6.21; f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <292b7a8ed84032cfdfc9076a690360f7d3f640d4; f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <113a9796effe3376d2ec5aabcca1fef4fef4cd62; patch: 7.2.7; f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <3da55616db2b6b7d9caa3b7ff1e8983224e0ed52; patch: 0; f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 <3525b94b2f258e0b99d1ee5a82a80b51bc1cc818

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.