Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 35 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 9fa1fb4a876e10cc17182ce339625ec4d4b75f20
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < bc988724973b7f50d5dd05637f1e9ef4f009afd5
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 338d6859cd1580617807290f6d7e92b1662d4695
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 757aa9f548c18b96da1d56d11f65be8188a16d59
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 3da55616db2b6b7d9caa3b7ff1e8983224e0ed52
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 292b7a8ed84032cfdfc9076a690360f7d3f640d4
    • affected f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 – < 113a9796effe3376d2ec5aabcca1fef4fef4cd62
  • Linux · Linux

    • affected 2.6.21
    • unaffected < 2.6.21
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97925 badge
[![CVE-2026-97925](https://cveledger.app/badge/CVE-2026-97925.svg)](https://cveledger.app/cve/CVE-2026-97925)

Record last updated .