ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]
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:
ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]
component_dais[RSND_MAX_COMPONENT] is initially zero-initialized and later populated in rsnd_dai_of_node(). However, the existing boundary check: if (i >= RSND_MAX_COMPONENT)
does not guarantee that the last valid element remains zero. As a result, the loop can rely on component_dais[RSND_MAX_COMPONENT] being zero, which may lead to an out-of-bounds access.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
From the CVE record · Linux
The Linux kernel’s ASoC rsnd code has a boundary-check flaw that can cause an out-of-bounds access while processing component_dais in rsnd_dai_of_node(). The input does not describe how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the ASoC rsnd component should check their versions against the Linux kernel advisory; affected versions are not specified here.