counter: rz-mtu3-cnt: prevent counter from being toggled multiple times
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
counter: rz-mtu3-cnt: prevent counter from being toggled multiple times
Runtime PM counter is incremented / decremented each time the sysfs enable file is written to.
If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message.
rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!
At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel.
If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0.
If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel.
From the CVE record · Linux
The Linux kernel's rz-mtu3-cnt counter mishandles repeated writes to its sysfs enable file. A local user able to write that file can underflow or unnecessarily increment the runtime PM usage count; a write of 0 during PWM operation can also stop PWM without the counter owning the channel.
Engineers running Linux kernels with the rz-mtu3-cnt counter should check their affected versions against the vendor advisory.