ALSA: timer: Set lower bound of start tick time
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bbaf5e97337287479eb78dbc3822d9560bbfd2e2 · < 2c95241ac5fc90c929d6c0c023e84bf0d30e84c3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: timer: Set lower bound of start tick time
Currently ALSA timer doesn't have the lower limit of the start tick time, and it allows a very small size, e.g. 1 tick with 1ns resolution for hrtimer. Such a situation may lead to an unexpected RCU stall, where the callback repeatedly queuing the expire update, as reported by fuzzer.
This patch introduces a sanity check of the timer start tick time, so that the system returns an error when a too small start size is set. As of this patch, the lower limit is hard-coded to 100us, which is small enough but can still work somehow.
From the CVE record · Linux
The Linux kernel’s ALSA timer accepts an excessively small start tick time. A caller that sets one can cause repeated timer callbacks and an unexpected RCU stall. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their systems; affected versions are not specified.