watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a7ceca4398bc835c6ad29d10e1106de4cf0332e1 · < 7cb575b71ab98194d2e040bded3a7281e089c5ed| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog
da9063_wdt_suspend() and da9063_wdt_resume() only check watchdog_active(), when the watchdog is left running by the driver sets WDOG_HW_RUNNING in da9063_wdt_probe() but userspace never opens the device, so WDOG_ACTIVE remains cleared, the wdt_disable() will not be executed in da9063_wdt_suspend. 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 WDOG_HW_RUNNING and wdd,can fix this issue.
From the CVE record · Linux
The Linux kernel's da9063 watchdog suspend handling can leave a hardware-running watchdog counting during system suspend. This can cause an unexpected system reset when userspace has never opened the watchdog device; the input does not describe an attacker or an exploitation path.
Operators running Linux systems that use the da9063 watchdog should check their kernel; affected versions are not specified.