CVE-2026-97969: Linux kernel · watchdog: msc313e: Fix clock leak and spurious timer in settimeout()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · 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.
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by correcting the watchdog timer start logic in settimeout(). Users should apply the official kernel updates containing this fix for the affected versions. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel watchdog driver for msc313e was resolved. The issue involved the msc313e_wdt_settimeout() function unconditionally calling msc313e_wdt_start(), causing two bugs: an unbalanced clock reference count when the watchdog is already active, and accidental starting of the hardware timer when the watchdog is stopped. The fix involved refactoring the register-writing logic to only start the timer if the watchdog is running, otherwise just updating the timeout value.
References
- ubuntu.com/security/CVE-2026-97969 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97969 (opens in a new tab)
- git.kernel.org/stable/c/2abf99a57b0b71b2b97745981f4039370ab78044 (opens in a new tab)
- git.kernel.org/stable/c/2152a13ee2a9af09a668ebd053a8dbf771dadb80 (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)
- nvd.nist.gov/vuln/detail/CVE-2026-97969 (opens in a new tab)
- 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)