CVE-2026-97969

Unintended reboot via stopped-watchdog timeout update

Published Sep 25, 2026 · Updated Sep 25, 2026

Improper watchdog state handling in affected Linux kernels allows local users to start a stopped hardware timer and trigger a reboot. msc313e_wdt_settimeout() calls the start routine even when the watchdog is stopped, enabling the clock and programming the timer instead of only recording the new timeout. Access to the MSC313e watchdog control path is required; repeated timeout changes while active also leak clock references.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Improper watchdog state handling in affected Linux kernels allows local users to start a stopped hardware timer and trigger a reboot. msc313e_wdt_settimeout() calls the start routine even when the watchdog is stopped, enabling the clock and programming the timer instead of only recording the new timeout. Access to the MSC313e watchdog control path is required; repeated timeout changes while active also leak clock references.

The record

CVE
CVE-2026-97969
Published
Sep 25, 2026
Updated
Sep 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1529
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.14
  2. Affected versionversion=e9800b7994642a794afd4894f072541c14277ce8 <2152a13ee2a9af09a668ebd053a8dbf771dadb80
  3. Affected versionversion=e9800b7994642a794afd4894f072541c14277ce8 <2abf99a57b0b71b2b97745981f4039370ab78044
  4. Affected versionversion=e9800b7994642a794afd4894f072541c14277ce8 <3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0
  5. Affected versionversion=e9800b7994642a794afd4894f072541c14277ce8 <faf1eb2895c87a8c0fb920439dddc7e0d97c6a69

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=5.14; version=e9800b7994642a794afd4894f072541c14277ce8 <2152a13ee2a9af09a668ebd053a8dbf771dadb80; version=e9800b7994642a794afd4894f072541c14277ce8 <2abf99a57b0b71b2b97745981f4039370ab78044; version=e9800b7994642a794afd4894f072541c14277ce8 <3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0; version=e9800b7994642a794afd4894f072541c14277ce8 <faf1eb2895c87a8c0fb920439dddc7e0d97c6a69

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1529System Shutdown/Reboot

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started