Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 113a9796effe3376d2ec5aabcca1fef4fef4cd62, 292b7a8ed84032cfdfc9076a690360f7d3f640d4, 338d6859cd1580617807290f6d7e92b1662d4695; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 113a9796effe3376d2ec5aabcca1fef4fef4cd62, 292b7a8ed84032cfdfc9076a690360f7d3f640d4, 338d6859cd1580617807290f6d7e92b1662d4695; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 25, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-97925

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.21affected
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 9fa1fb4a876e10cc17182ce339625ec4d4b75f20affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before bc988724973b7f50d5dd05637f1e9ef4f009afd5affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 338d6859cd1580617807290f6d7e92b1662d4695affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 757aa9f548c18b96da1d56d11f65be8188a16d59affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 3da55616db2b6b7d9caa3b7ff1e8983224e0ed52affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 3525b94b2f258e0b99d1ee5a82a80b51bc1cc818affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 292b7a8ed84032cfdfc9076a690360f7d3f640d4affected · git
    • f8381cba04ba8173fd5a2b8e5cd8b3290ee13a98 and later · before 113a9796effe3376d2ec5aabcca1fef4fef4cd62affected · git
    • before 2.6.21not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.7-17.2.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-97923Sep 25, 2026 · tracing: Free histogram the var ref when its initialization fails
    0Monitor
  • ← EarlierCVE-2026-97924Sep 25, 2026 · tracing/user_events: Don't destroy fields when event removal fails
    0Monitor
  • Later →CVE-2026-97926Sep 25, 2026 · ufs: validate cylinder group metadata before caching it
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux113a9796effe3376d2ec5aabcca1fef4fef4cd62Vendor (CNA)
Linux Linux292b7a8ed84032cfdfc9076a690360f7d3f640d4Vendor (CNA)
Linux Linux338d6859cd1580617807290f6d7e92b1662d4695Vendor (CNA)
Linux Linux3525b94b2f258e0b99d1ee5a82a80b51bc1cc818Vendor (CNA)
Linux Linux3da55616db2b6b7d9caa3b7ff1e8983224e0ed52Vendor (CNA)
Linux Linux757aa9f548c18b96da1d56d11f65be8188a16d59Vendor (CNA)
Linux Linux9fa1fb4a876e10cc17182ce339625ec4d4b75f20Vendor (CNA)
Linux Linuxbc988724973b7f50d5dd05637f1e9ef4f009afd5Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records