CVE-2026-97969

watchdog: msc313e: Fix clock leak and spurious timer in settimeout()

N/A
Published: September 25, 2026 at 10:23 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: watchdog: msc313e: Fix clock leak and spurious timer in settimeout() msc313e_wdt_settimeout() unconditionally calls msc313e_wdt_start() which introduces two severe bugs: 1. If the watchdog is already active, calling start() again will increase the reference count of the clock again. However stop() is only called once, the reference count is unbalance. 2. If the watchdog is stopped, calling settimeout() will start the hardware timer accidentally. Factor out the register-writing logic into a helper function. Only call it in settimeout() if the watchdog is running. Otherwise, simply update `wdev->timeout`.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.14e9800b7994642a794afd4894f072541c14277ce8
Vendor states this is fixed in 2152a13ee2a9af09a668ebd053a8dbf771dadb80 (fixed)
Vendor states this is fixed in 2abf99a57b0b71b2b97745981f4039370ab78044 (fixed)
Vendor states this is fixed in 3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0 (fixed)
Vendor states this is fixed in 68665016c7b777b44e27b6b0c1e6524c28ebe40a (fixed)
Vendor states this is fixed in 77ef2aa8b46876ca9935f32dd874c517ccf5d880 (fixed)
Vendor states this is fixed in a1dd0817776ea2a870ba2347001af13ddd4cb321 (fixed)
Vendor states this is fixed in faf1eb2895c87a8c0fb920439dddc7e0d97c6a69 (fixed)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card