Affected: Linux

In the Linux kernel, the following vulnerability has been resolved:

watchdog: msc313e: Fix clock leak and spurious timer in settimeout()

msc313e_wdt_settimeout() unconditionally calls msc313e_wdt_start() which introduces two severe bugs:

1. If the watchdog is already active, calling start() again will increase the reference count of the clock again. However stop() is only called once, the reference count is unbalance. 2. If the watchdog is stopped, calling settimeout() will start the hardware timer accidentally.

Factor out the register-writing logic into a helper function. Only call it in settimeout() if the watchdog is running. Otherwise, simply update `wdev->timeout`.