CVE-2026-97969

Unknown

Last modified

CVE-2026-97969 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e9800b7994642a794afd4894f072541c14277ce8, < 2152a13ee2a9af09a668ebd053a8dbf771dadb80; >= e9800b7994642a794afd4894f072541c14277ce8, < 2abf99a57b0b71b2b97745981f4039370ab78044; >= e9800b7994642a794afd4894f072541c14277ce8, < faf1eb2895c87a8c0fb920439dddc7e0d97c6a69; >= e9800b7994642a794afd4894f072541c14277ce8, < 3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0
LinuxLinux5.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97969?
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`.
How severe is CVE-2026-97969?
Severity scoring for CVE-2026-97969 is pending analysis.
How do I fix CVE-2026-97969?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97969?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST