Unexpected reboot via missed watchdog hardware-running state
Published Oct 14, 2026 · Updated Oct 14, 2026
A watchdog state-check error in Linux 5.19 allows attackers to cause an unexpected system reboot during suspend on DA9063 hardware. The da9063_wdt_suspend() and da9063_wdt_resume() callbacks check WDOG_ACTIVE but ignore WDOG_HW_RUNNING, leaving the timer counting when userspace has never opened the watchdog device. The affected path requires dlg,use-sw-pm configuration and a running hardware watchdog; suspend lasting beyond its timeout triggers a reset, and the published evidence does not establish attacker privileges or a remote trigger.
Summary
What happened
A watchdog state-check error in Linux 5.19 allows attackers to cause an unexpected system reboot during suspend on DA9063 hardware. The da9063_wdt_suspend() and da9063_wdt_resume() callbacks check WDOG_ACTIVE but ignore WDOG_HW_RUNNING, leaving the timer counting when userspace has never opened the watchdog device. The affected path requires dlg,use-sw-pm configuration and a running hardware watchdog; suspend lasting beyond its timeout triggers a reset, and the published evidence does not establish attacker privileges or a remote trigger.
The record
- CVE
- CVE-2026-98410
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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.
- Affected versionversion=5.19
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <1c42e39b0990371b9d76ae22c3f33eb6df341251
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <1db134d0d2a51a136296584854570e5e04adedb0
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <7cb575b71ab98194d2e040bded3a7281e089c5ed
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <95adc37f47cdf5a5285f7163b24243680af510be
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <960d1c85381bcaae866dd799b1c905ec5d39ebce
- Affected versionversion=a7ceca4398bc835c6ad29d10e1106de4cf0332e1 <c30b419c7e6fbe31c48a44c828174168b732dc5b
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
No sourced classifications are available.
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