UBUNTU-CVE-2026-98410: Medium severity ubuntu/linux-hwe-edge vulnerability
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.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which systems are exposed to unexpected resets?
Systems using the DA9063 watchdog driver are affected when the hardware watchdog is left running and the system enters suspend. The issue applies when userspace has not opened the watchdog device, leaving the watchdog active in hardware without the WDOG_ACTIVE state being set.
What triggers the reset?
During suspend, the affected driver checks only whether the watchdog is active from userspace. If the hardware watchdog is running but the device was never opened, suspend does not disable it, so it continues counting and can reset the system while suspended.
What can be done before an update is available?
Avoid suspending systems where the DA9063 hardware watchdog has been left running without userspace opening the watchdog device. Ensuring the watchdog is managed through the watchdog device prevents the specific unchecked hardware-running state described.
How can I recognize this issue in practice?
A likely symptom is an unexpected system reset during or after suspend on a system using the DA9063 watchdog. The relevant condition is a watchdog configured as hardware-running while the watchdog device has not been opened by userspace.