ASoC: ops: Fix bounds check for _sx controls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e8e07c5e25a29e2a6f119fd947f55d7a55eb8a13 · < 98b15c706644bebc19d2e77ccc360cc51444f6d0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: ops: Fix bounds check for _sx controls
For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.
From the CVE record · Linux
The Linux kernel's snd_soc_put_volsw_sx() function uses an incorrect bounds check for ASoC _sx controls because their max field represents the number of steps, not the maximum value. The input does not specify what an attacker could do or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions were not provided.