CVE-2026-98410: watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog
In the Linux kernel, the following vulnerability has been resolved:
watchdog: da9063: fix suspend/resume handling of HWRUNNING watchdog
da9063wdtsuspend() and da9063wdtresume() only check watchdogactive(), when the watchdog is left running by the driver sets WDOGHWRUNNING in da9063wdtprobe() but userspace never opens the device, so WDOGACTIVE remains cleared, the wdtdisable() will not be executed in da9063wdtsuspend. In this case, the suspend callback is a no-op and the watchdog keeps counting during system suspend, leading to an unexpected system reset. Check WDOGHWRUNNING and wdd，can fix this issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Update da9063_wdt_suspend() and da9063_wdt_resume() to account for WDOG_HW_RUNNING, so a watchdog left running by the driver is properly handled during suspend and does not cause an unexpected system reset.
Linux kernel da9063 watchdog driver suspend/resume watchdog state handling = Check WDOG_HW_RUNNING in the watchdog device state (wdd)
Event History
Frequently Asked Questions
Which systems are exposed to the unexpected reset condition?
Systems using the Linux kernel DA9063 watchdog driver are exposed when the watchdog is configured as hardware-running (WDOG_HW_RUNNING) but userspace has never opened the watchdog device. In that state, WDOG_ACTIVE remains unset.
When does the reset occur?
The watchdog continues counting while the system is suspended because the suspend callback does not disable it. If the watchdog timeout expires during suspend, the system can reset unexpectedly.
Does userspace need to interact with the watchdog device for this to happen?
No. The affected case specifically occurs when userspace never opens the watchdog device, leaving WDOG_ACTIVE cleared even though the watchdog is running in hardware.
What behavior does the fix change?
The fix makes suspend and resume handling account for WDOG_HW_RUNNING as well as the watchdog device state, so a hardware-running watchdog is handled even when it is not marked active by userspace.