watchdog: msc313e: Fix clock leak and spurious timer in settimeout()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e9800b7994642a794afd4894f072541c14277ce8 · < faf1eb2895c87a8c0fb920439dddc7e0d97c6a69| No fix yet |
| Linux 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`.
From the CVE record · Linux
The Linux kernel’s msc313e watchdog settimeout() can increment the clock reference count again when the watchdog is active, or start the hardware timer when it is stopped. The input does not describe an attacker or specify access, authentication, or user-interaction conditions.
Engineers running Linux kernels with the msc313e watchdog should check their versions; affected versions are not specified.