CVE-2026-97969: Linux kernel · watchdog: msc313e: Fix clock leak and spurious timer in settimeout()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in faf1eb2895c87a8c0fb920439dddc7e0d97c6a69 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:21 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in faf1eb2895c87a8c0fb920439dddc7e0d97c6a69, a1dd0817776ea2a870ba2347001af13ddd4cb321, 68665016c7b777b44e27b6b0c1e6524c28ebe40a +4
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel source code as indicated by multiple fixed commit versions. Users should update to a kernel version that includes these fixes to resolve the clock leak and spurious timer issues in the msc313e watchdog driver.
Description
A vulnerability in the Linux kernel watchdog driver msc313e was fixed to address a clock reference count leak and an unintended hardware timer start when setting a timeout. The issue arose because the watchdog start function was called unconditionally, causing reference count imbalance and spurious timer activation.
References
- git.kernel.org/stable/c/68665016c7b777b44e27b6b0c1e6524c28ebe40a (opens in a new tab)
- git.kernel.org/stable/c/77ef2aa8b46876ca9935f32dd874c517ccf5d880 (opens in a new tab)
- git.kernel.org/stable/c/a1dd0817776ea2a870ba2347001af13ddd4cb321 (opens in a new tab)
- git.kernel.org/stable/c/2152a13ee2a9af09a668ebd053a8dbf771dadb80 (opens in a new tab)
- git.kernel.org/stable/c/2abf99a57b0b71b2b97745981f4039370ab78044 (opens in a new tab)
- git.kernel.org/stable/c/faf1eb2895c87a8c0fb920439dddc7e0d97c6a69 (opens in a new tab)
- git.kernel.org/stable/c/3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0 (opens in a new tab)